Re: Couldn't umount on /mnt/md0-device busy???

["bo" <bo@sosnetwork.net>]

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.

How do I remove(erase) those information from lockd?
Where is the file "statd"?

Thanks,

Bo
----- Original Message -----
From: "Ross Vandegrift" <ross@willow.seitz.com>
To: "bo" <bo@sosnetwork.net>
Cc: "Mike Black" <mblack@csi-inc.com>; <linux-raid@vger.kernel.org>
Sent: Thursday, July 18, 2002 10:47 AM
Subject: Re: Couldn't umount on /mnt/md0-device busy???


> 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
>