umount -f

perryh at perryh at
Tue Jun 12 03:49:53 UTC 2007

> > > 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.

umount -f should not corrupt the filesystem, IOW "fsck" of an
FS immediately after "umount -f" should not report anything
more serious than some homeless files (if the last link had
been removed, but the inode had not been released because some
process still had it open).

However data corruption seems likely if it yanks the rug
out from under a process that has, say, written part of a
transaction to a database file.

More information about the freebsd-questions mailing list