From: Andrew Morton <akpm@zip.com.au>
To: Steffen Persvold <sp@scali.no>
Cc: lkml <linux-kernel@vger.kernel.org>,
nfs list <nfs@lists.sourceforge.net>,
ext2-devel@lists.sourceforge.net
Subject: Re: 2.4.9 kernel crash
Date: Fri, 30 Nov 2001 12:16:05 -0800 [thread overview]
Message-ID: <3C07E905.DF30E497@zip.com.au> (raw)
In-Reply-To: <3C077FF8.AFBD8DB8@scali.no>
Steffen Persvold wrote:
>
> Hi all,
>
> This just happened to my RedHat 7.2 box running the 2.4.9-13 update kernel from RedHat. The box is
> running as a NFS server, exporting two ext3 volumes (one 36GB and one 73GB) :
>
> VFS: Busy inodes after unmount. Self-destruct in 5 seconds. Have a nice day...
There was a bug in ext3 which was fixed around about the 2.4.9
timeframe. I don't know if the fix is present in that
particular Red Hat kernel. It was fixed in ext3 0.9.8. The
ext3 version number is displayed when you mount a filesystem.
The 0.9.8 changelog says:
- Fix an NFS oops when doing a local delete on an active, nfs-exported
file.
I never observed this bug - I think the fix came from Ted T'so. I
do not know whether the bug manifested itself as "busy inodes
after unmount". Perhaps Ted or Stephen can comment?
next prev parent reply other threads:[~2001-11-30 20:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-30 12:47 2.4.9 kernel crash Steffen Persvold
2001-11-30 20:16 ` Andrew Morton [this message]
2001-12-03 19:10 ` [NFS] " Stephen Walton
2001-12-04 0:32 ` [Ext2-devel] " Stephen C. Tweedie
2001-12-04 0:33 ` [Ext2-devel] " Stephen C. Tweedie
2001-12-06 18:26 ` Steffen Persvold
2001-12-06 18:50 ` Stephen C. Tweedie
2001-12-06 20:52 ` [NFS] " Ragnar Kjørstad
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=3C07E905.DF30E497@zip.com.au \
--to=akpm@zip.com.au \
--cc=ext2-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=nfs@lists.sourceforge.net \
--cc=sp@scali.no \
/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.