From: "Stephen C. Tweedie" <sct@redhat.com>
To: Andrew Morton <akpm@zip.com.au>
Cc: Steffen Persvold <sp@scali.no>,
lkml <linux-kernel@vger.kernel.org>,
nfs list <nfs@lists.sourceforge.net>,
ext2-devel@lists.sourceforge.net
Subject: Re: [Ext2-devel] Re: 2.4.9 kernel crash
Date: Tue, 4 Dec 2001 00:33:50 +0000 [thread overview]
Message-ID: <20011204003350.L2857@redhat.com> (raw)
In-Reply-To: <3C077FF8.AFBD8DB8@scali.no> <3C07E905.DF30E497@zip.com.au>
In-Reply-To: <3C07E905.DF30E497@zip.com.au>; from akpm@zip.com.au on Fri, Nov 30, 2001 at 12:16:05PM -0800
Hi,
On Fri, Nov 30, 2001 at 12:16:05PM -0800, Andrew Morton wrote:
> 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?
The NFS bug could present as "bit already cleared", but I don't think
I ever saw it leave busy inodes behind.
Cheers,
Stephen
next prev parent reply other threads:[~2001-12-04 0:35 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
2001-12-03 19:10 ` [NFS] " Stephen Walton
2001-12-04 0:32 ` [Ext2-devel] " Stephen C. Tweedie
2001-12-04 0:33 ` Stephen C. Tweedie [this message]
2001-12-06 18:26 ` [Ext2-devel] " 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=20011204003350.L2857@redhat.com \
--to=sct@redhat.com \
--cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox