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 > doing a log look-up always fail is inefficient so I checked the code path that set inode's logged_trans field. Oh ok, I thought you were trying to make sure it was relogged, so I read this wrong. You're assuming that if it was ever logged we don't need to log it again, which does look correct. Thanks for the patch. -chris -- 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
