Re: [PATCH v2] Btrfs: fix file/data loss caused by fsync after rename and new inode

2016-09-03 Thread Chris Mason
On 08/18/2016 11:03 AM, Chris Mason wrote: On Wed, Mar 30, 2016 at 11:37:21PM +0100, fdman...@kernel.org wrote: From: Filipe Manana If we rename an inode A (be it a file or a directory), create a new inode B with the old name of inode A and under the same parent directory,

Re: [PATCH v2] Btrfs: fix file/data loss caused by fsync after rename and new inode

2016-08-18 Thread Chris Mason
On Wed, Mar 30, 2016 at 11:37:21PM +0100, fdman...@kernel.org wrote: From: Filipe Manana If we rename an inode A (be it a file or a directory), create a new inode B with the old name of inode A and under the same parent directory, fsync inode B and then power fail, at log

Re: [PATCH v2] Btrfs: fix file/data loss caused by fsync after rename and new inode

2016-03-31 Thread Chris Mason
On Wed, Mar 30, 2016 at 11:37:21PM +0100, fdman...@kernel.org wrote: > From: Filipe Manana > > If we rename an inode A (be it a file or a directory), create a new > inode B with the old name of inode A and under the same parent directory, > fsync inode B and then power fail,

Re: [PATCH v2] Btrfs: fix file/data loss caused by fsync after rename and new inode

2016-03-31 Thread Duncan
fdmanana posted on Wed, 30 Mar 2016 23:37:21 +0100 as excerpted: > From: Filipe Manana > > If we rename an inode A (be it a file or a directory), create a new > inode B with the old name of inode A and under the same parent > directory, fsync inode B and then power fail, at

[PATCH v2] Btrfs: fix file/data loss caused by fsync after rename and new inode

2016-03-31 Thread fdmanana
From: Filipe Manana If we rename an inode A (be it a file or a directory), create a new inode B with the old name of inode A and under the same parent directory, fsync inode B and then power fail, at log tree replay time we end up removing inode A completely. If inode A is a