Re: [Bug-tar] [PATCH] Re: Detection of sparse files is broken on btrfs

2018-01-09 Thread Paul Eggert
Pavel Raiskup wrote: So what about special casing that filesystem, where we can lseek() for holes anyway? If we can lseek for holes, then why not just do that? We shouldn't need special-case code for btrfs per se. Any filesystem where we can lseek for holes should take advantage of that

Re: [Bug-tar] stat() on btrfs reports the st_blocks with delay (data loss in archivers)

2016-07-06 Thread Paul Eggert
On 07/06/2016 05:09 PM, Joerg Schilling wrote: you concur that a delayed assignment of the "correct" value for st_blocks while the contend of the file does not change is not permitted. I'm not sure I agree even with that. A file system may undergo garbage collection and compaction, for

Re: [Bug-tar] stat() on btrfs reports the st_blocks with delay (data loss in archivers)

2016-07-06 Thread Paul Eggert
On 07/06/2016 04:53 PM, Joerg Schilling wrote: Antonio Diaz Diaz wrote: >Joerg Schilling wrote: > >POSIX requires st_blocks to be != 0 in case that the file contains data. > >Please, could you provide a reference? I can't find such requirement at