From mboxrd@z Thu Jan 1 00:00:00 1970 From: "bo" Subject: Re: Couldn't umount on /mnt/md0-device busy??? Date: Thu, 18 Jul 2002 17:43:50 -0700 Sender: linux-raid-owner@vger.kernel.org Message-ID: <000501c22ebd$59bc3b40$5701a8c0@bomoon> References: <15668.41627.988382.451061@notabene.cse.unsw.edu.au> <003c01c22db8$57b86590$5701a8c0@bomoon> <3D35BCD6.7030300@cfht.hawaii.edu> <06d001c22def$eaa10510$5701a8c0@bomoon> <009d01c22e54$54d968a0$f6de11cc@black> <073d01c22e7e$299d8020$5701a8c0@bomoon> <20020718174720.GD4712@willow.seitz.com> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Return-path: To: Ross Vandegrift Cc: Mike Black , linux-raid@vger.kernel.org List-Id: linux-raid.ids 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" To: "bo" Cc: "Mike Black" ; 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 >