From: Joel Becker <Joel.Becker@oracle.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [PATCH 1/1] Ocfs2: Stop tracking a negative dentry after dentry_iput().
Date: Wed, 17 Nov 2010 15:23:44 -0800 [thread overview]
Message-ID: <20101117232344.GF25677@mail.oracle.com> (raw)
In-Reply-To: <1289828349-24098-1-git-send-email-tristan.ye@oracle.com>
On Mon, Nov 15, 2010 at 09:39:09PM +0800, Tristan Ye wrote:
> I suddenly hit the problem during 2.6.37-rc1 regression test, which was
> introduced by commit '5e98d492406818e6a94c0ba54c61f59d40cefa4a'(Track
> negative entries v3), following scenario reproduces the issue easily:
>
> Node A Node B
> ================ ============
> $touch testfile
> $ls testfile
> $rm -rf testfile
> $touch testfile
> $ls testfile
> ls: cannot access testfile: No such file or directory
>
> This patch stops tracking the dentry which was negativated by a inode deletion,
> so as to force the revaliation in next lookup, in case we'll touch the inode
> again in the same node.
>
> It didn't hurt the performance of multiple lookup for none-existed files anyway,
> while regresses a bit in the first try after a file deletion.
I'm going to take this fix for now, because it is clearing the
problem. However, it looks like the original code _should_ work. If we
have created a file, the directory's generation should have been
updated. Thus, the pgen shouldn't match the generation set when the old
inode was deleted. Right?
Joel
--
Life's Little Instruction Book #237
"Seek out the good in people."
Joel Becker
Senior Development Manager
Oracle
E-mail: joel.becker at oracle.com
Phone: (650) 506-8127
next prev parent reply other threads:[~2010-11-17 23:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-15 13:39 [Ocfs2-devel] [PATCH 1/1] Ocfs2: Stop tracking a negative dentry after dentry_iput() Tristan Ye
2010-11-17 23:23 ` Joel Becker [this message]
2010-11-18 1:42 ` Tristan Ye
2010-11-18 2:08 ` Tristan Ye
2010-11-18 23:38 ` Joel Becker
2010-11-18 23:43 ` Joel Becker
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=20101117232344.GF25677@mail.oracle.com \
--to=joel.becker@oracle.com \
--cc=ocfs2-devel@oss.oracle.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.