From: Chris Mason <chris.mason@oracle.com>
To: Itaru Kitayama <kitayama@cl.bb4u.ne.jp>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH] Log parent inode if it is newer than the last commit
Date: Mon, 08 Nov 2010 15:26:08 -0500 [thread overview]
Message-ID: <1289247820-sup-7675@think> (raw)
In-Reply-To: <20101108232751.3a6cecd0.kitayama@cl.bb4u.ne.jp>
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
prev parent reply other threads:[~2010-11-08 20:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-06 11:03 [PATCH] Log parent inode if it is newer than the last commit Itaru Kitayama
2010-11-06 14:19 ` Josef Bacik
2010-11-08 13:50 ` Chris Mason
2010-11-08 14:27 ` Itaru Kitayama
2010-11-08 20:26 ` Chris Mason [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1289247820-sup-7675@think \
--to=chris.mason@oracle.com \
--cc=kitayama@cl.bb4u.ne.jp \
--cc=linux-btrfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).