Date: Sun, 28 Jun 2009 21:53:04 -0700 From: David G Lawrence <dg@dglawrence.com> To: Rick Macklem <rmacklem@uoguelph.ca> Cc: freebsd-fs@freebsd.org, freebsd-current@freebsd.org Subject: Re: umount -f implementation Message-ID: <20090629045304.GI39302@tnn.dglawrence.com> In-Reply-To: <Pine.GSO.4.63.0906281955160.5084@muncher.cs.uoguelph.ca> References: <Pine.GSO.4.63.0906281955160.5084@muncher.cs.uoguelph.ca>
next in thread | previous in thread | raw e-mail | index | archive | help
> 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. I would say that you are seeing a bug. -f is supposed to mean "force", of course. Any buffers or outstanding transactions should be terminated immediately. Oh, and most of us know that you, as one of the NFS developers in the past, well-know the difference between hard and soft NFS mounts. ;-) -DG David G. Lawrence President Download Technologies, Inc. - http://www.downloadtech.com - (866) 399 8500 Pave the road of life with opportunities.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20090629045304.GI39302>