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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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
-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux RAID Wiki]     [ATA RAID]     [Linux SCSI Target Infrastructure]     [Linux Block]     [Linux IDE]     [Linux SCSI]     [Linux Hams]     [Device Mapper]     [Device Mapper Cryptographics]     [Kernel]     [Linux Admin]     [Linux Net]     [GFS]     [RPM]     [git]     [Yosemite Forum]


  Powered by Linux