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 13:47:20 -0400 [thread overview]
Message-ID: <20020718174720.GD4712@willow.seitz.com> (raw)
In-Reply-To: <073d01c22e7e$299d8020$5701a8c0@bomoon>
On Thu, Jul 18, 2002 at 10:11:31AM -0700, bo wrote:
> Mike,
>
> It does not matter with the order in /etc/exports.
> This "umount" problem goes away when I remove "/mnt/md0" entry from
> /etc/exports. I have 3 more;/mnt/md1, /mnt/md2, /mnt/md3 without any
> problem.
>
> I think system has a special meaning with "/mnt/md0". What does it do???
Perhaps:
1) A remote machine has a mount of /mnt/md0
2) Your server has a stale mount record for /mnt/md0
3) Something has wacked out lockd, which is keeping stuff locked
Try "showmount" and see if any machines have your filesystems mounted
when you think they shouldn't.
If some machine has a stale NFS mount, you may need to clear out the
saved statd information.
Ross Vandegrift
ross@willow.seitz.com
next prev parent reply other threads:[~2002-07-18 17:47 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 [this message]
2002-07-19 0:43 ` bo
2002-07-19 0:58 ` Ross Vandegrift
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=20020718174720.GD4712@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).