From: Ross Vandegrift <ross@willow.seitz.com>
To: bo <bo@sosnetwork.net>
Cc: Mike Black <mblack@csi-inc.com>, linux-raid@vger.kernel.org
Subject: Re: Couldn't umount on /mnt/md0-device busy???
Date: Thu, 18 Jul 2002 20:58:24 -0400 [thread overview]
Message-ID: <20020719005823.GA9116@willow.seitz.com> (raw)
In-Reply-To: <000501c22ebd$59bc3b40$5701a8c0@bomoon>
On Thu, Jul 18, 2002 at 05:43:50PM -0700, bo wrote:
> Yes, you may be right.
> >showmount
> Host on P300
> 10.0.0.2
> 192.168.1.151
>
> It looks like it got the old mount information from manufacturing test.
> I do not have those connections(users) now.
I do not know if this is the kosher, most correct way to do this, but
look at the files in /var/lib/nfs (that's where they are on my Slackware
box, and a Debian machine at work).
There's a bunch of files in there that have NFS mount info. Make sure
all clients actually have it umounted, shutdown NFS and nuke that dir
(well, move it to someplace else, and recreated it in case it blows up).
You could probably edit it and remove the non-existant client as well,
but I haven't ever done it this way.
Ross Vandegrift
ross@willow.seitz.com
next prev parent reply other threads:[~2002-07-19 0:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-16 22:17 reconstruction stalls Michael Robinton
2002-07-16 22:47 ` Neil Brown
2002-07-17 17:35 ` Couldn't umount on /mnt/md0-device busy??? bo
2002-07-17 18:52 ` Kanoalani Withington
2002-07-18 0:13 ` bo
[not found] ` <009d01c22e54$54d968a0$f6de11cc@black>
2002-07-18 17:11 ` bo
2002-07-18 17:47 ` Ross Vandegrift
2002-07-19 0:43 ` bo
2002-07-19 0:58 ` Ross Vandegrift [this message]
2002-07-19 1:49 ` Kanoalani Withington
2002-07-20 8:32 ` Egon Eckert
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=20020719005823.GA9116@willow.seitz.com \
--to=ross@willow.seitz.com \
--cc=bo@sosnetwork.net \
--cc=linux-raid@vger.kernel.org \
--cc=mblack@csi-inc.com \
/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).