Date: Tue, 3 Dec 1996 14:45:31 -0700 (MST) From: Terry Lambert <terry@lambert.org> To: imp@village.org (Warner Losh) Cc: hackers@FreeBSD.org Subject: Re: But it didn't work. Message-ID: <199612032145.OAA14694@phaeton.artisoft.com> In-Reply-To: <199612032050.NAA29676@rover.village.org> from "Warner Losh" at Dec 3, 96 01:50:20 pm
next in thread | previous in thread | raw e-mail | index | archive | help
> OK. I was able to unexport /jaz by restarting mountd after hacking > /etc/exports. However, unmount still says the drive is busy. lsof | egrep /jaz > (where I have it mounted) yields no output. > > Ideas? (1) There is a file open on the drive (2) There is a directory open on the drive A file requires a program. List the open fd's, and find the offending program. A directory requires only that the program was started on that drive. Where you *on* the jaz drive when you started mountd? That would do it. If you look at the mount code, it's obvious that the NFS mount list handling is done in each FS's mount code (and unmount code). A plain "umount" should have unexported the FS, automatically... or rather, it should have made the directory for the mount point theexported FS. In either case, the mountd doesn't have the thing open all the time, so it *can't* be the guy holding the partition "busy". The exports list is just that: a list. It is *NOT* a reference to the object, apart from the code in mount. That's why the export code should be seperate and layerd above the mount (it would also mean that any new FS would "just work" with NFS, instead of needing it's mount code special cased). You are running UFS on the drive, right? Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199612032145.OAA14694>