On Wed, 30 May 2007 10:28:57 +1000
David Chinner <[EMAIL PROTECTED]> wrote:
> On Tue, May 29, 2007 at 11:40:42AM -0400, Jeff Layton wrote:
> > After spending quite a bit of time tracking down a "VFS: busy inodes
> > after unmount" problem, it occurs to me that it would be nice to be
> > able to fo
On Tue, May 29, 2007 at 11:40:42AM -0400, Jeff Layton wrote:
> After spending quite a bit of time tracking down a "VFS: busy inodes
> after unmount" problem, it occurs to me that it would be nice to be
> able to force a panic when that occurs. While an oops message alone is
> not generally helpful
would be nice to be
> > able to force a panic when that occurs. While an oops message alone is
> > not generally helpful for tracking down this sort of problem,
> > collecting and analyzing a coredump when this occurs can be.
> >
> > The following patch adds a procfs tu
not generally helpful for tracking down this sort of problem,
> collecting and analyzing a coredump when this occurs can be.
>
> The following patch adds a procfs tunable that allows you to force a
> core when a "busy inodes after umount" problem occurs. It also changes
>
nalyzing a coredump when this occurs can be.
The following patch adds a procfs tunable that allows you to force a
core when a "busy inodes after umount" problem occurs. It also changes
the classic error message to be something a bit less cryptic to users.
Signed-off-by: Jeff Layton <[
Hi Ian,
On Sunday 24 July 2005 04:12, Ian Kent wrote:
> If the automount daemon receives a signal which causes it to sumarily
> terminate the autofs4 module leaks dentries. The same problem exists with
> detached mount requests without the warning.
>
> This patch cleans these dentries at umount.
nclude
#include
+#include
#include "autofs_i.h"
#include
@@ -76,6 +77,66 @@
kfree(ino);
}
+/*
+ * Deal with the infamous "Busy inodes after umount ..." message.
+ *
+ * Clean up the dentry tree. This happens with autofs if the user
+ * space program goes away
On Thu, Jul 19, 2001 at 07:38:15PM -0500, Tad Dolphay wrote:
> I know there was a fix for a "Busy inodes after unmount" problem in
> 2.4.6-pre3. Here's an excerpt from a posting to the NFS mailing list
> from Neil Brown:
Thanks. I'll try that and see if that solves the problem (also the XFS
UUID
I know there was a fix for a "Busy inodes after unmount" problem in
2.4.6-pre3. Here's an excerpt from a posting to the NFS mailing list
from Neil Brown:
-Included message---
Previously anonymous dentries were hashed (though with no name, the
hash was pretty me
I reported this a couple of months back. It's reassuring to know that it's a
consistent problem.
On Fri, 20 Jul 2001, [iso-8859-1] Ragnar Kjørstad wrote:
> On Thu, Jul 19, 2001 at 04:22:07PM -0400, Christian, Chip wrote:
> > I found the same thing happening. Tracked it down in our case to usin
On Thu, Jul 19, 2001 at 04:22:07PM -0400, Christian, Chip wrote:
> I found the same thing happening. Tracked it down in our case to using fdisk to
>re-read disk size before mounting. Replaced it with "blockdev --readpt" and the
>problem seems to have gone away. YMMV.
I've now been able to re
Hi,
Here is how I manage to hit this under 2.4.0-test11-pre6
1. mkfs an ext2 filesystem on a 36G disk
2. do a complex combination of data and metadata io on it by means
of SPECsfs with LOADs high enough to run out of space
3. observe that both high and low memory are almost zero, i.e. about
12 matches
Mail list logo
