Re: [PATCH] Btrfs: no full sync flag on new inode when we do not reuse inode id

[Liu Bo <bo.li.liu@oracle.com>]

On Wed, Dec 12, 2012 at 09:50:04AM -0500, Josef Bacik wrote:
> On Tue, Dec 11, 2012 at 06:43:04PM -0700, Liu Bo wrote:
> > On Tue, Dec 11, 2012 at 10:01:17AM -0500, Josef Bacik wrote:
> > > On Thu, Dec 06, 2012 at 08:11:54PM -0700, Liu Bo wrote:
> > > > When we are not with inode_cache option, we won't reuse inode id, which
> > > > means all of inodes will own different inode id, thus we don't worry
> > > > about "reuse of inode id leads to log tree's corruption" thing.
> > > > 
> > > > Signed-off-by: Liu Bo <bo.li.liu@oracle.com>
> > > 
> > > With the new fsync stuff I have I still need to make sure all new xattrs and
> > > such are on disk so this needs to stay the way it is.  Thanks,
> > 
> > So with new fsync we cannot bare any old items even if their keys's
> > objectid(actually inode id) are different, is it right?
> > 
> 
> No its more that I need to know that I should log everything related to the
> inode, xattrs and all.  Otherwise I'll just log the inode item and make selinux
> very sad.  Thanks,
> 
> Josef

Oh, I see, I've mixed with another different problem, sorry.

thanks,
liubo