Re: [PATCH] Log parent inode if it is newer than the last commit

I've been puzzled why I see a flood of ENOENT returned upon rename during Fedora 13 and 14's GDM session. The case is of course handled by your recent patch which is in upstream and btrfs-unstable, but I thought doing a log look-up always fail is inefficient so I checked the code path that

Re: [PATCH] Log parent inode if it is newer than the last commit

Excerpts from Itaru Kitayama's message of 2010-11-08 09:27:51 -0500: I've been puzzled why I see a flood of ENOENT returned upon rename during Fedora 13 and 14's GDM session. The case is of course handled by your recent patch which is in upstream and btrfs-unstable, but I thought

[PATCH] Log parent inode if it is newer than the last commit

In the file sync path, file's parent inode is logged if it is newer than the last commit. This patch checks also the last_trans field as well as generation. As btrfs_log_inode updates the logged_trans field of parent dir's inode, tree-log lookup operations are suppressed upon unlink. The

Re: [PATCH] Log parent inode if it is newer than the last commit

On Sat, Nov 06, 2010 at 08:03:05PM +0900, Itaru Kitayama wrote: In the file sync path, file's parent inode is logged if it is newer than the last commit. This patch checks also the last_trans field as well as generation. As btrfs_log_inode updates the logged_trans field of parent dir's