From: Felipe Alfaro Solana <felipe_alfaro@linuxmail.org>
To: Florian Huber <florian.huber@mnet-online.de>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: Can't unmount NFS - System freezes
Date: 16 Jun 2003 23:58:15 +0200 [thread overview]
Message-ID: <1055800694.586.6.camel@teapot.felipe-alfaro.com> (raw)
In-Reply-To: <20030616224504.0132cc1b.florian.huber@mnet-online.de>
On Mon, 2003-06-16 at 22:45, Florian Huber wrote:
> if I try to unmount a NFS-mounted directory my system freezes.
> There is neither a error message nor a log entry.
>
> I can't type anymore, but the NUM-Lock LED can still be switched
> on/off. The host is also not ping-able.
>
> I also tried different mount options (nfsvers=3, nfsvers=2, default or
> even my former 2.4.x settings).
>
> The NFS server is a 2.4.20 machine exporting with rw,async.
> The client is using 2.5.71 (same with 2.5.70-mm9).
>
> I'm sorry that I can't give you a more detailed description of the
> problem. Perhaps you can give me some hints how to debug this.
Can you try to reproduce this from the console? I've seen this behavior
on previous versions of the kernel, and also the related kernel panic on
the console. It would be interesting if you could gather the OOPS
message and attach it in a message.
I would also suggest trying the following patch if you can:
http://www.kernel.org/pub/linux/kernel/people/akpm/patches/2.5/2.5.71/2.5.71-mm1/broken-out/rpc-depopulate-fix.patch
Or else, the latest 2.5.71-bk snapshot to see if it's fixed. At least,
I've been unable to reproduce previous NFS crashes on 2.5.71-mm1.
prev parent reply other threads:[~2003-06-16 21:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-16 20:45 Florian Huber
2003-06-16 21:58 ` Felipe Alfaro Solana [this message]
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=1055800694.586.6.camel@teapot.felipe-alfaro.com \
--to=felipe_alfaro@linuxmail.org \
--cc=florian.huber@mnet-online.de \
--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
all inboxes | Powered by JetHome®