All of lore.kernel.org
 help / color / mirror / Atom feed
From: Goutham Kurra <kurrag1@yahoo.com>
To: nfs@lists.sourceforge.net
Subject: force unmount not working 2.4.22
Date: Sat, 9 Oct 2004 14:22:31 -0700 (PDT)	[thread overview]
Message-ID: <20041009212231.78436.qmail@web20524.mail.yahoo.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0410091031520.1370@donald.themaw.net>


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 notice that rpc_killall_tasks() is called from the
umount_begin(), but none of the processes get an EIO.
They continue to work as before.

I've also noticed this on stock RH 2.4.20-9 kernels.

Any idea what's going on?

Thanks!
g



		
__________________________________
Do you Yahoo!?
Take Yahoo! Mail with you! Get it on your mobile phone.
http://mobile.yahoo.com/maildemo 


-------------------------------------------------------
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-09 21:22 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   ` Goutham Kurra [this message]
2004-10-09 21:41     ` force unmount not working 2.4.22 Garrick Staples
2004-10-11 22:09       ` Goutham Kurra
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=20041009212231.78436.qmail@web20524.mail.yahoo.com \
    --to=kurrag1@yahoo.com \
    --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.