From: Itai Nahshon <nahshon@actcom.co.il>
To: linux-kernel@vger.kernel.org
Subject: [OT] unable to umount ... device busy
Date: Tue, 27 Aug 2002 01:40:04 +0300 [thread overview]
Message-ID: <200208270140.04743.nahshon@actcom.co.il> (raw)
Well, sorry for bringing this up here3 but I do not know
of a better forum for this subject...
Working in an environment of multiple Linux systems
(and wildly using NFS and am-utils) I have hit this problem
many times and in some cases I can describe it as "embarrassing".
The problem is that processes that do not really care about their
working directory are standing in the way of umount.
It is most painful when I cannot eject a CD (or other removable
device) and sometimes with NFS mounted directories.
Most guilty programs:
su + the pam patch (as distributed by redhat) there's a process just
waiting for the shell to exit.
Daemons - should cd to "/" except if there is some other preferred
directory.
Related subject and not completely OT: I remember in AIX, umount -f
(forced umount) marked all the open inodes on the device as
STALE and then proceed (and never return EBUSY). Any plans
to implement it also for Linux?
-- Itai
reply other threads:[~2002-08-26 22:35 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200208270140.04743.nahshon@actcom.co.il \
--to=nahshon@actcom.co.il \
--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®