AW: umount -f implementation

In practice, there are situations where one does want to get rid of a non reachable mounpoint (specifically for NFS) which basically is not possible as of today.

A fix in case the -f (or another new flag like) were supplied, would be highly appreciated.

Thanks,
Gunther


--
SmApper Technologies GmbH – +43 5372 6912 640 – www.smapper.com

----- Originalnachricht -----
Von: owner-freebsd-fs_at_freebsd.org <owner-freebsd-fs_at_freebsd.org>
An: freebsd-current_at_freebsd.org <freebsd-current_at_freebsd.org>
Cc: freebsd-fs_at_freebsd.org <freebsd-fs_at_freebsd.org>
Gesendet: Mon Jun 29 02:00:13 2009
Betreff: umount -f implementation

I just noticed that when I do the following:
- start a large write to an NFS mounted fs
- network partition the server (unplug a net cable)
- do a "umount -f <mntpoint>" on the machine

that it gets stuck trying to write dirty blocks to the server.

I had, in the past, assumed that a "umount -f" of an NFS mount would be
used to get rid of an NFS mount on an unresponsive server and that loss
of "writes in progress" would be expected to happen.

Does that sound correct? (In other words, an I seeing a bug or a 
feature?)

Thanks in advance for any info, rick
ps: I have a simple "fix" if this is a bug, but I wanted to check before
     submitting a patch.
_______________________________________________
freebsd-fs_at_freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-fs

To unsubscribe, send any mail to "freebsd-fs-unsubscribe_at_freebsd.org"