From: Soeren Sonnenburg <kernel@nn7.de>
To: Oleg Drokin <green@namesys.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: kswapd oops in 2.4.20 SMP+NFS
Date: 21 Mar 2003 10:50:47 +0100 [thread overview]
Message-ID: <1048240247.9345.19.camel@fortknox> (raw)
In-Reply-To: <20030321112834.A17330@namesys.com>
On Fri, 2003-03-21 at 09:28, Oleg Drokin wrote:
> Hello!
>
> On Thu, Mar 20, 2003 at 03:23:24PM +0100, Soeren Sonnenburg wrote:
>
> > I got the following oops recently. The machine is still up and running
> > and was working stably for a year now...
> > Linux 2.4.20 #1 SMP Tue Dec 10 11:16:20 CET 2002 i686 unknown
> > 2 x AMD K7-MP 1200MHz PCI(5-64) TYAN Thunder K7 S2462 Mainboard 1G ECC Memory
> > [...]
> > nfsd-fh: found a name that I didn't expect: sys/oz
> > nfsd-fh: found a name that I didn't expect: sys/oz
> > nfsd-fh: found a name that I didn't expect: bin/x86
> > nfsd-fh: found a name that I didn't expect: bin/x86
> > nfsd-fh: found a name that I didn't expect: etc/bla
> > VFS: Busy inodes after unmount. Self-destruct in 5 seconds. Have a nice day...
>
> Hm, what is the underlying host filesystem?
oops sorry, it is running ext2 on the smaller disks... and reiserfs
everywhere else but the above files were on a reiserfs partition which
is rather young (i.e. has not seen anything else than kernel 2.4.20)...
Soeren
next prev parent reply other threads:[~2003-03-21 9:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-20 14:23 kswapd oops in 2.4.20 SMP+NFS Soeren Sonnenburg
2003-03-21 8:28 ` Oleg Drokin
2003-03-21 8:36 ` Soeren Sonnenburg
2003-03-21 9:50 ` Soeren Sonnenburg [this message]
2003-03-21 10:04 ` Oleg Drokin
[not found] ` <1048243299.9338.23.camel@fortknox>
[not found] ` <20030321135841.D17440@namesys.com>
2003-03-21 11:20 ` Soeren Sonnenburg
2003-03-21 13:56 ` Oleg Drokin
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=1048240247.9345.19.camel@fortknox \
--to=kernel@nn7.de \
--cc=green@namesys.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox