From: James Pearson <james-p@moving-picture.com>
To: Thomas Moestl <moestl@ibr.cs.tu-bs.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: umount() and NFS races in 2.4.26
Date: Fri, 09 Jul 2004 16:00:50 +0100 [thread overview]
Message-ID: <40EEB322.40002@moving-picture.com> (raw)
Thomas Moestl:
>after deploying an SMP machine at work, we started to experience Oopses
>in file-system related code relatively frequently. Investigation
>revealed that they were caused by references using junk pointers from
>freed super blocks via dangling inodes from unmounted file systems;
>Oopses would always be preceded by the warning
> VFS: Busy inodes after unmount. Self-destruct in 5 seconds. Have a
nice day...
>on an unmount (unmount activity is high on this machine due to heavy
>use of the automounter).
Are you using the latest autofs4 kernel patches?
I had a similar problem - see the thread at:
http://marc.theaimsgroup.com/?l=linux-nfs&m=108515468003933&w=2
The latest autofs4 patches fixed it for me - available from:
http://www.kernel.org/pub/linux/daemons/autofs/v4
James Pearson
next reply other threads:[~2004-07-09 15:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-09 15:00 James Pearson [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-07-08 18:07 umount() and NFS races in 2.4.26 Thomas Moestl
2004-07-09 14:32 ` Marcelo Tosatti
2004-07-10 21:38 ` Trond Myklebust
2004-07-11 0:32 ` viro
2004-07-10 6:57 ` raven
2004-07-10 18:19 ` Thomas Moestl
2004-07-10 19:25 ` raven
2004-07-10 19:25 ` raven
2004-07-10 19:50 ` Thomas Moestl
2004-07-11 10:16 ` raven
2004-07-11 10:16 ` raven
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=40EEB322.40002@moving-picture.com \
--to=james-p@moving-picture.com \
--cc=linux-kernel@vger.kernel.org \
--cc=moestl@ibr.cs.tu-bs.de \
/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.