From: David Chinner <dgc@sgi.com>
To: Jim Paradis <jparadis@exagrid.com>
Cc: xfs@oss.sgi.com
Subject: Re: Duplicate directory entries
Date: Thu, 20 Mar 2008 15:35:57 +1100 [thread overview]
Message-ID: <20080320043557.GX95344431@sgi.com> (raw)
In-Reply-To: <D9A1816327F7BF4F931ADE74C248DFC90A42D366@it-004.Isys.com>
On Wed, Mar 19, 2008 at 11:32:42PM -0400, Jim Paradis wrote:
> David Chinner:
> >On Wed, Mar 19, 2008 at 03:26:05PM -0400, Jim Paradis wrote:
> >> We recently ran across a situation where we saw two directory entries
> >> that were exactly the same.
> >
> >What kernel version?
>
> 2.6.18.
No, it was originnally diagnosed on 2.6.5 kernels (sles9) and was fixed around
2.6.17 by the inode i_sem -> i_mutex conversion in mainline before we tracked
it down. The root problem there was a semaphore lock leak in the direct I/O
code causing problems when the inode was recycled and reused as a directory.
The system would panic in the dentry cache, but log recovery would result in
creating duplicate entries in the directory.
I don't think this is your problem unless you've only recently upgraded
from an old kernel and your applications do direct I/O.....
Can you reproduce the problem or provide any information on events
that may have occurred around the time of the duplicates being created?
I suspect that a reproducable test case will be the only way we can track
this down....
Cheers,
Dave.
--
Dave Chinner
Principal Engineer
SGI Australian Software Group
next prev parent reply other threads:[~2008-03-20 4:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-19 19:26 Duplicate directory entries Jim Paradis
2008-03-19 23:48 ` Barry Naujok
2008-03-20 0:02 ` David Chinner
2008-03-20 3:32 ` Jim Paradis
2008-03-20 4:35 ` David Chinner [this message]
2008-03-21 18:29 ` Jim Paradis
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=20080320043557.GX95344431@sgi.com \
--to=dgc@sgi.com \
--cc=jparadis@exagrid.com \
--cc=xfs@oss.sgi.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox