Re: [PATCH] Btrfs: fix loss of prealloc extents past i_size after fsync log replay

On Tue, Apr 10, 2018 at 01:50:21PM +, Sasha Levin wrote: > Hi, > > [This is an automated email] > > This commit has been processed because it contains a "Fixes:" tag, > fixing commit: c71bf099abdd Btrfs: Avoid orphan inodes cleanup while > replaying log. > > The bot has also determined

Re: [PATCH] Btrfs: fix loss of prealloc extents past i_size after fsync log replay

Hi, [This is an automated email] This commit has been processed because it contains a "Fixes:" tag, fixing commit: c71bf099abdd Btrfs: Avoid orphan inodes cleanup while replaying log. The bot has also determined it's probably a bug fixing patch. (score: 6.2138) The bot has tested the

Re: [PATCH] Btrfs: fix loss of prealloc extents past i_size after fsync log replay

On Thu, Apr 05, 2018 at 10:55:12PM +0100, fdman...@kernel.org wrote: > From: Filipe Manana > > Currently if we allocate extents beyond an inode's i_size (through the > fallocate system call) and then fsync the file, we log the extents but > after a power failure we replay them