umount -f

Kris Kennaway kris at obsecurity.org
Tue Jun 12 01:24:30 UTC 2007


On Mon, Jun 11, 2007 at 08:17:14PM -0400, Bill Moran wrote:
> Modulok <modulok at gmail.com> wrote:
> >
> > Couple questions for anyone on the list who has a moment (and the answer to
> > any of these):
> > 
> > Objective: I need to kick people off of a storage drive (we'll say
> > /dev/ad4), without corrupting the file system and without bringing the
> > entire system down. I need to safely umount the file systems, even if my
> > users have processes which have files open.
> > 
> > 1. If I use "umount -f /dev/ad4s1a" to forcefully umount a file system, does
> > this jeopardize the integrity of said file system? Like...will it jerk the
> > run out from under a process in the middle of a disk write, thus leaving a
> > half written file, or will it wait until the write is complete? (I guess
> > this would largely depend on the disk controller?)
> 
> I don't believe there are any guarantees if your -f it.  The filesystem
> will probably be OK, but I would expect files to get corrupt.

Shouldn't happen, if it does it's a bug.

Kris


More information about the freebsd-questions mailing list