From: Robert Myers <rmyers1400@attbi.com>
To: Johan van Reijendam <jvanreij@routescience.com>
Cc: nfs@lists.sourceforge.net
Subject: Re: NFS unmounts fail
Date: Sun, 22 Dec 2002 20:02:29 -0500 [thread overview]
Message-ID: <3E0660A5.9090607@attbi.com> (raw)
In-Reply-To: <3E06524D.1030608@routescience.com>
Johan van Reijendam wrote:
> Hi all,
>
> I have been unable to find the cause and a solution for this problem
>
> I am mounting NFS filesystems. Both the client and the server are
> running Redhat 7.3. The problem is the following :
>
> I am able to mount a filesystem (automount or otherwise ) and can
> browse that filesystem. When I pull out of that filesystem automount
> will unmount it after a while and if manually mounted I am then able
> to manually unmount it.
> However whenever I execute a binary from the mounted filesystem I am
> no longer able to unmount that filesystem. The message I get is:
>
> umount: umount2: Device or resource busy
> umount: umount: /auto/packages/binaries: device is busy
>
> Neither lsof or fuser report any open files.
The most frequent cause of inexplicable "Device or resource is busy"
messages when attempting an unmount has been that the device or some
directory of the device is theoretically visible from Nautilus. In
those cases, closing the /mnts tab on the Nautilus tree and moving the
view window to some other directory usually solves the problem.
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
prev parent reply other threads:[~2002-12-23 1:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-23 0:01 NFS unmounts fail Johan van Reijendam
2002-12-23 1:02 ` Robert Myers [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=3E0660A5.9090607@attbi.com \
--to=rmyers1400@attbi.com \
--cc=jvanreij@routescience.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.