public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Martin J. Bligh" <mbligh@aracnet.com>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: umount -f /nfsmount hangs
Date: Thu, 19 Aug 2004 14:51:10 -0700	[thread overview]
Message-ID: <268300000.1092952270@flay> (raw)
In-Reply-To: <1092950791.3810.85.camel@lade.trondhjem.org>

--On Thursday, August 19, 2004 17:26:31 -0400 Trond Myklebust <trond.myklebust@fys.uio.no> wrote:

> På to , 19/08/2004 klokka 16:55, skreiv Martin J. Bligh:
>> NFS server has gone away, was mounted soft, intr:
>> 
>> bvrgsa.ibm.com:/gsa/bvrgsa on /bvrgsa type nfs (rw,soft,intr,nfsvers=2,tcp,rsize=8192,wsize=8192,timeo=30,addr=9.47.56.70)
>> 
>> but umount -f just hangs ... surely that's not the intended behaviour?
>> from Alt+SysRq+t:
> 
> Works fine for me with 2.6.8.1 and the Fedora Core2 2.6.7-based kernel.
> If you physically turn off the server as opposed to just killing the
> nfsd processes, then it takes a bit longer than for the networking layer
> to time out the sock_release etc (isn't that under the control of the
> tcp_fin_timeout sysctl?), but AFAICS it does eventually get there.
> 
> Are there any other details you're omitting?

Yeah, it did time out eventually and yes, the network got disconnected
rather than killing nfsd. I guess I was expecting -f to mean "Do it. Now" ...
However, the damned thing is still mounted as listed by "mount".

Viro pointed me to -l as well ... -f -l seems to work OK.

M.


      reply	other threads:[~2004-08-19 21:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-19 20:55 umount -f /nfsmount hangs Martin J. Bligh
2004-08-19 21:26 ` Trond Myklebust
2004-08-19 21:51   ` Martin J. Bligh [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=268300000.1092952270@flay \
    --to=mbligh@aracnet.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox