Re: btrfs crash consistency bug : Blocks allocated beyond eof are lost

On Fri, Feb 23, 2018 at 4:35 PM, Jayashree Mohan wrote: > Hi, > > [Fsync issue in btrfs] > In addition to the above, I would like to bring to your notice that : > After doing a fallocate or fallocate zero_range with keep size option, > a fsync() operation would have no

Re: btrfs crash consistency bug : Blocks allocated beyond eof are lost

Hi, [Fsync issue in btrfs] In addition to the above, I would like to bring to your notice that : After doing a fallocate or fallocate zero_range with keep size option, a fsync() operation would have no effect at all. If we crash after the fsync, on recovery the blocks allocated due to the

btrfs crash consistency bug : Blocks allocated beyond eof are lost

Hi, On btrfs (as of kernel 4.15), say we fallocate a file with keep_size option, followed by fdatasync() or fsync(). If we now crash, on recovery we see a wrong block count and all the blocks allocated beyond the eof are lost. This bug was reported(xfstest generic/468) and patched on ext4[1], and