All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bill Davidsen <davidsen@tmr.com>
To: Brice Goglin <Brice.Goglin@ens-lyon.org>
Cc: trond.myklebust@fys.uio.no, linux-kernel@vger.kernel.org
Subject: Re: Crash when unmounting NFS/TCP with -f
Date: Fri, 22 Apr 2005 14:43:24 -0400	[thread overview]
Message-ID: <426945CC.6040100@tmr.com> (raw)
In-Reply-To: <4268EEC9.8010305@ens-lyon.org>

Brice Goglin wrote:
> 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).
> 
> Do you have any idea how to debug this ?

No clue, but a question: is this a hard or soft mount? Could you post 
your ssh and mount commands, munged as needed for security? That might 
give someone a clue.

I did this "back when" but I don't recall having a problem with it.

-- 
    -bill davidsen (davidsen@tmr.com)
"The secret to procrastination is to put things off until the
  last possible moment - but no longer"  -me


  parent reply	other threads:[~2005-04-25 16:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-22 12:32 Crash when unmounting NFS/TCP with -f Brice Goglin
2005-04-22 13:39 ` Trond Myklebust
2005-04-22 18:43 ` Bill Davidsen [this message]
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=426945CC.6040100@tmr.com \
    --to=davidsen@tmr.com \
    --cc=Brice.Goglin@ens-lyon.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=trond.myklebust@fys.uio.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.