From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Brice Goglin <Brice.Goglin@ens-lyon.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Crash when unmounting NFS/TCP with -f
Date: Fri, 22 Apr 2005 09:39:10 -0400 [thread overview]
Message-ID: <1114177150.10450.49.camel@lade.trondhjem.org> (raw)
In-Reply-To: <4268EEC9.8010305@ens-lyon.org>
fr den 22.04.2005 Klokka 14:32 (+0200) skreiv Brice Goglin:
> Hi Trond,
>
> I'm using NFS (v2) over TCP (in a SSH tunnel).
> Each time the SSH dies before a umount NFS, I have to umount -f
> and I get a crash (only sysrq works).
> Actually, the crash occurs a few seconds after umount -f.
>
> It seems that killing SSH by hand does _not_ lead to crash.
> But a long network failure does.
> I remember seeing this bug several times with all stable releases
> from 2.6.7 to 2.6.11. I didn't try with earlier versions.
>
> I didn't see anything in the logs (after reboot). But I can't be sure
> there was nothing in dmesg since I didn't get a chance to chvt 1 and
> see console messages before rebooting (with sysrq).
I'll try to reproduce. There has just been a discussion about "umount
-f" on the NFS mailing list (nfs@lists.sourceforge.net), where Peter
Cendio said he was seeing the following Oops:
http://www.cendio.se/~peter/fc3-umount-crash.png
I am unable to reproduce Peter's crash, but I didn't try the scenario
that you describe above.
Cheers,
Trond
--
Trond Myklebust <trond.myklebust@fys.uio.no>
next prev parent reply other threads:[~2005-04-22 13:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-22 12:32 Brice Goglin
2005-04-22 13:39 ` Trond Myklebust [this message]
2005-04-22 18:43 ` Bill Davidsen
2005-04-26 7:51 ` Brice Goglin
2005-05-05 10:17 ` Brice Goglin
2005-05-05 11:58 ` Trond Myklebust
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=1114177150.10450.49.camel@lade.trondhjem.org \
--to=trond.myklebust@fys.uio.no \
--cc=Brice.Goglin@ens-lyon.org \
--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®