Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*GNU\s+\'tar\'\,\s+Schilling\'s\s+\'tar\'\,\s+write\-cache\/barrier\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*GNU\s+\'tar\'\,\s+Schilling\'s\s+\'tar\'\,\s+write\-cache\/barrier\s*$/: 3 ]

Total 3 documents matching your query.

1. GNU 'tar', Schilling's 'tar', write-cache/barrier (score: 1): Author: pg_xf2@xxxxxxxxxxxxxxxxxx (Peter Grandi); Date: Sat, 24 Mar 2012 16:27:19 +0000; [ ... ] As to this, I have realized that there is a very big detail that I have given for implicit but that perhaps at this point should be made explicit as to the deliberately misleading propaganda; /archives/xfs/2012-03/msg00465.html (26,336 bytes)
2. Re: GNU 'tar', Schilling's 'tar', write-cache/barrier (score: 1): Author: Brian Candler <B.Candler@xxxxxxxxx>; Date: Sat, 24 Mar 2012 17:11:50 +0000; But as a user, what guarantees do I *want* from tar? I think the only meaningful guarantee I might want is: "if the tar returns successfully, I want to know that all the files are persisted to disk".; /archives/xfs/2012-03/msg00471.html (13,782 bytes)
3. Re: GNU 'tar', Schilling's 'tar', write-cache/barrier (score: 1): Author: pg_xf2@xxxxxxxxxxxxxxxxxx (Peter Grandi); Date: Sat, 24 Mar 2012 18:35:46 +0000; [ ... ] Ahhhh, but that depends *a lot* on the application, that may or may not be 'tar', and what you are using 'tar' for. Consider for example restoring a backup using RSYNC instead of 'tar'. Perha; /archives/xfs/2012-03/msg00473.html (14,298 bytes)

Current List: 1 - 3
Page: [1]