atom feed15 messages in org.freebsd.freebsd-fsumount -f implementation
FromSent OnAttachments
Rick MacklemJun 28, 2009 4:59 pm 
Nathanael HoyleJun 28, 2009 5:31 pm 
David G LawrenceJun 28, 2009 9:52 pm 
Attilio RaoJun 29, 2009 2:55 am 
Rick MacklemJun 29, 2009 7:38 am 
Rick MacklemJun 29, 2009 8:16 am 
Bruce EvansJun 29, 2009 10:52 am 
Rick C. PettyJun 29, 2009 4:26 pm 
Rick MacklemJun 30, 2009 9:00 am 
Attilio RaoJun 30, 2009 9:07 am 
Kostik BelousovJun 30, 2009 12:32 pm 
Rick MacklemJun 30, 2009 1:03 pm 
Kirk McKusickJun 30, 2009 2:58 pm 
Julian H. StaceyJun 30, 2009 5:48 pm 
Rick MacklemJul 1, 2009 10:26 am 
Subject:umount -f implementation
From:Rick Macklem (rmac@uoguelph.ca)
Date:Jun 28, 2009 4:59:50 pm
List:org.freebsd.freebsd-fs

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.

_______________________________________________ free@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-fs To unsubscribe, send any mail to "free@freebsd.org"