All of lore.kernel.org
 help / color / mirror / Atom feed
From: Goutham Kurra <kurrag1@yahoo.com>
To: Garrick Staples <garrick@usc.edu>, nfs@lists.sourceforge.net
Subject: Re: force unmount not working 2.4.22
Date: Mon, 11 Oct 2004 15:09:42 -0700 (PDT)	[thread overview]
Message-ID: <20041011220942.96898.qmail@web20525.mail.yahoo.com> (raw)
In-Reply-To: <20041009214156.GV7742@polop.usc.edu>



I can see that '-f' tries to stop all active rpc tasks
to the server, but I guess the reference counts on the
mount are not dropped. What would be cool is a
'brute-force' option that kills any process that still
holds a reference to the filesystem and then also
unmounts it. 

The problem with using something like fuser is that it
will promptly hang on an unreachable server making it
useless on nfs filesystems. 

Any ideas on what to do in this case (i.e, unreachable
NFS server, plus a bunch of processes hung on the
mount)?

I'm uncomfortable using lazy unmounts as I don't have
a way of knowing if the filesystem has finally been
dropped or not.

goutham


--- Garrick Staples <garrick@usc.edu> wrote:

> On Sat, Oct 09, 2004 at 02:22:31PM -0700, Goutham
> Kurra alleged:
> > 
> > Force unmount simply isn't working on a standard
> linux
> > 2.4.22 kernel. Isn't it supposed to unmount NFS
> > filesystems no matter what?
> > 
> > In my case, the backend server is still up and
> > working, I have a "tail -f /mnt/nfs/foo" of some
> file
> > on the mount, and "umount -f" fails with "device
> or
> > resource is busy"
> 
> I don't believe force is useful in this case, what
> you want is -l.
> 
>    -f     Force unmount (in case of an unreachable
> NFS system).  (Requires
>           kernel 2.1.116 or later.)
> 
>    -l     Lazy unmount. Detach the filesystem from
> the filesystem  hierar-
>           chy now, and cleanup all references to the
> filesystem as soon as
>           it is not busy anymore.  (Requires kernel
> 2.4.11 or later.)
> 
> -- 
> Garrick Staples, Linux/HPCC Administrator
> University of Southern California
> 

> ATTACHMENT part 2 application/pgp-signature 




		
__________________________________
Do you Yahoo!?
Yahoo! Mail Address AutoComplete - You start. We finish.
http://promotions.yahoo.com/new_mail 


-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

  reply	other threads:[~2004-10-11 22:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-07 13:31 NFS and/or autofs hanging on Linux Burke, Alan
2004-10-09  2:34 ` raven
2004-10-09 21:22   ` force unmount not working 2.4.22 Goutham Kurra
2004-10-09 21:41     ` Garrick Staples
2004-10-11 22:09       ` Goutham Kurra [this message]
2004-10-11 22:55         ` Michael Richardson

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=20041011220942.96898.qmail@web20525.mail.yahoo.com \
    --to=kurrag1@yahoo.com \
    --cc=garrick@usc.edu \
    --cc=nfs@lists.sourceforge.net \
    /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.