Re: 5.1-BETA umount problems
From: Ian Dowse (iedowse_at_maths.tcd.ie)
Date: 05/19/03
- Previous message: Ian Dowse: "Re: kgdb missing stack frames"
- In reply to: David Schultz: "Re: 5.1-BETA umount problems"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
To: David Schultz <das@FreeBSD.ORG> Date: Mon, 19 May 2003 10:46:40 +0100
In message <20030519051855.GB4396@HAL9000.homeunix.com>, David Schultz writes:
>umount -f can be extremely useful on a multiuser system when you
>*really* want to unmount a filesystem regardless of who might be
>trying to use it. However, it also makes it easy to shoot
>yourself in the foot. If it only fails in situations where you
>are absolutely guaranteed to shoot yourself in the foot, that's
>fine. There's no reason it should allow someone to unmount a
>filesystem that contains a mountpoint for another mounted
>filesystem.
I've had some patches floating around for a while that change
unmount() so that filesystems can be unmounted by specifying the
filesystem ID instead of a path. This helps a lot in the unmounting
of NFS mounts from dead servers, as it avoids any lookups that might
hang indefinitely, but it should also make it possible to unmount
filesystems that get detached from the filesystem they were mounted
over. I was holding off on committing this in the hopes of finding
a cleaner way of passing a fsid_t through unmount()'s `const char
*dir' argument. Patch is at:
http://www.maths.tcd.ie/~iedowse/FreeBSD/umount_by_fsid.diff
Ian
_______________________________________________
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
- Previous message: Ian Dowse: "Re: kgdb missing stack frames"
- In reply to: David Schultz: "Re: 5.1-BETA umount problems"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
|
