From: Felipe Alfaro Solana <felipe_alfaro@linuxmail.org>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: Bojan Smojver <bojan@rexursive.com>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: 2.5.68: NFS3+exported /mnt/cdrom+eject: system lockup
Date: 01 May 2003 13:56:00 +0200 [thread overview]
Message-ID: <1051790160.1960.6.camel@teapot.felipe-alfaro.com> (raw)
In-Reply-To: <shsd6j3gdan.fsf@charged.uio.no>
On Thu, 2003-05-01 at 12:40, Trond Myklebust wrote:
> >>>>> " " == Bojan Smojver <bojan@rexursive.com> writes:
>
> > NFS3 server was running on the box and it was exporting a
> > mounted /mnt/cdrom to the world. On "umount /mnt/cdrom" it
> > reported "device busy". On "eject /mnt/cdrom" it locked the
> > system hard.
>
> > What kind of information would help debugging this?
>
> The only bug there is the hard crash. You are never allowed to unmount
> a device that has been exported.
What about not being able to unmount a filesystem that was once
exported, but now it's not? I've been experiencing this problem since a
long time ago:
I have a volume/partition exported via NFS:
/data 192.168.0.100(rw,no_root_squash) 192.168.0.0/24(ro)
However, during shutdown (it's a RH9 box), I do get "can't unmount,
device is busy" errors while unmounting this filesystem *after* the NFS
server has been stopped and all shares unexported.
This does only occurs if the shared NFS volume has been used by other
clients on the LAN. If no client tries to mount/use the share, this
doesn't happen.
Anyways, I'm having problems with NFS on 2.5... many programs fail when
accessing files over NFS, normally, programs that perform heavy file
seeks, writes and reads, like "oggdec" or "lame". They usually can't
complete without exitting with errors.
More information can be provided on detail :-)
--
Please AVOID sending me WORD, EXCEL or POWERPOINT attachments.
See http://www.fsf.org/philosophy/no-word-attachments.html
Linux Registered User #287198
next prev parent reply other threads:[~2003-05-01 11:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-01 1:56 2.5.68: NFS3+exported /mnt/cdrom+eject: system lockup Bojan Smojver
2003-05-01 10:40 ` Trond Myklebust
2003-05-01 11:56 ` Felipe Alfaro Solana [this message]
2003-05-01 12:07 ` Trond Myklebust
2003-05-01 22:55 ` Bojan Smojver
2003-05-02 0:11 ` Trond Myklebust
2003-05-02 0:59 ` Bojan Smojver
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=1051790160.1960.6.camel@teapot.felipe-alfaro.com \
--to=felipe_alfaro@linuxmail.org \
--cc=bojan@rexursive.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;
as well as URLs for NNTP newsgroup(s).