From: Anders Peter Fugmann <afu@fugmann.dhs.org>
To: Daniel Freedman <freedman@ccmr.cornell.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: NFS stale mount after chroot...
Date: Mon, 10 Dec 2001 13:06:56 +0100 [thread overview]
Message-ID: <3C14A560.1020501@fugmann.dhs.org> (raw)
In-Reply-To: <20011209205707.A13073@ccmr.cornell.edu>
I see the same, though I have not tried to chroot.
It happens when I have run mozilla from a NFS mounted fs.
Both client and server is 2.4.16, but I have had this problem with older
kernels. NFSv3 support is compiled in both kernels.
lsof and fuser reports that no files are in use, but I'm unable to
unmount the filesystem. Btw. The filesystem is mounted ro. (and exported
ro). The exported filesystem is a reiser-fs.
I would really be greatfull if this issue was to be resolved.
Thanks in advance
Anders Fugmann
On 12/10/2001 02:57 AM, Daniel Freedman wrote:
> Hi,
>
> It seems like I can generate reproducible stale NFS mounts by mounting
> a partition, chroot'ing into that mount, immediately exiting the
> chroot, and then finding myself unable to unmount the NFS partition.
> I'm pretty sure I've confirmed that nothing is using the partition
> (both with fuser and lsof) and even tried to force umount the
> partition (which seems like it should definitely umount it, rather
> than returning with the same "device is busy" errors), to no avail.
> The only method which I've used that seems to be able to get rid of
> this NFS mount, is to reboot the NFS client, and clearly that's not a
> good one at all. If I'm missing something obvious here, my apologies
> in advance. Also, if there's any further information I can provide,
> I'd be happy to help. The dump of my procedure follows this message.
>
> Thanks again and take care,
> Daniel
>
>
next prev parent reply other threads:[~2001-12-10 12:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-10 1:57 NFS stale mount after chroot Daniel Freedman
2001-12-10 2:18 ` Daniel Freedman
2001-12-10 12:06 ` Anders Peter Fugmann [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-12-10 3:42 Tyler BIRD
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=3C14A560.1020501@fugmann.dhs.org \
--to=afu@fugmann.dhs.org \
--cc=freedman@ccmr.cornell.edu \
--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