Neil Brown writes:
> On Wednesday January 29, mikpe@csd.uu.se wrote:
> > Kernel 2.5.59. A local ext2 file system is mounted at $MNTPNT
> > and exported through NFS V3. A client mounts and unmounts it,
> > w/o any I/O in between. The NFS server is shut down. Nothing in
> > user-space refers to $MNTPNT.
> >
> > The bug is that $MNTPNT now can't be unmounted. umount fails with
> > "device is busy". A forced umount at shutdown fails with "device
> > or resource busy" and "illegal seek", and leaves the underlying
> > fs marked dirty.
> >
> > I can't say exactly when this began, but the problem is present
> > in 2.5.59 and 2.5.55. 2.4.21-pre4 does not have this problem.
>
> How do you shut down the nfs server?
/etc/rc.d/init.d/nfs stop
which basically does a kill on rpc.mountd, nfsd, and rpc.quotad
(standard RH8.0 user-space)
I've checked that all *nfs* processes are gone.
> Is anything in /proc/fs/nfs/export after the shutdown?
Except for the two header lines, it's empty.
/Mikael
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Fri Jan 31 2003 - 22:00:23 EST