From: Balbir Singh <balbir@in.ibm.com>
To: David Chinner <dgc@sgi.com>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] Per-superblock unused dentry LRU lists V2
Date: Thu, 25 May 2006 11:59:57 +0530 [thread overview]
Message-ID: <20060525062957.GC25185@in.ibm.com> (raw)
In-Reply-To: <20060525061553.GC8069029@melbourne.sgi.com>
>
> FWIW, this create/unlink load has been triggering reliable "Busy
> inodes after unmount" errors that I've slowly been tracking down.
> After I fixed the last problem in XFS late last week, I've
> been getting a failure that i think is the unmount/prune_dcache
> races that you and Neil have recently fixed.
Good, we were not able to reproduce the problem and test the fix.
I guess we have a more reliable way of testing the fix now.
>
> Basically, I'm seeing a transient elevated reference count on
> the root inode of the XFS filesystem during the final put_super()
> in generic_shutdown_super(). If I trigger a BUG_ON() when that
> elevated reference count is detected, byt he time al the cpus
> are stopped and I'm in kdb, the reference count on the root inode
> is only 1. The next thing I was going to track was where the dentry
> for the root inodes was.
The dput() would happen eventually, in this case after the umount.
kprobes might be more reliable for extracting information in this
case.
>
> I'll know if this really is the same race soon, as the create/unlink
> test would trip it under an hour.....
>
> Cheers,
>
> Dave.
Cheers,
Balbir Singh,
Linux Technology Center,
IBM Software Labs
next prev parent reply other threads:[~2006-05-25 6:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-24 11:00 [PATCH] Per-superblock unused dentry LRU lists V2 David Chinner
2006-05-24 11:00 ` David Chinner
2006-05-25 4:06 ` Balbir Singh
2006-05-25 4:06 ` Balbir Singh
2006-05-25 6:15 ` David Chinner
2006-05-25 6:15 ` David Chinner
2006-05-25 6:29 ` Balbir Singh [this message]
2006-05-25 6:33 ` David Chinner
2006-05-25 6:33 ` David Chinner
2006-05-25 6:52 ` Balbir Singh
2006-05-25 6:52 ` Balbir Singh
2006-05-25 8:13 ` David Chinner
2006-05-26 0:24 ` David Chinner
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=20060525062957.GC25185@in.ibm.com \
--to=balbir@in.ibm.com \
--cc=dgc@sgi.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@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 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.