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@xxxxxxxxxx> > > 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? Actually I made this patch to try to skip the expensive committing transaction in a 'create & write & fsync' test. thanks, liubo -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
