On Thu, 2013-10-17 at 10:35 -0700, Ben Greear wrote: +AD4- On 10/15/2013 11:29 AM, Ben Greear wrote: +AD4- +AD4- Is 'umount -f' supposed to always work, even if the file server +AD4- +AD4- goes away? +AD4- +AD4- +AD4- +AD4- I have a user's system that just hangs forever in this case. +AD4- +AD4- +AD4- +AD4- Could be local changes we have made, but I'm curious about +AD4- +AD4- the expected behaviour before I go digging too deep... +AD4- +AD4- Any input on this? I don't mind trying to fix it, but I +AD4- would like to know how it is supposed to work. 'umount -f' has always been iffy. It just kills any pending RPC calls +AF8-before+AF8- trying to unmount. Since the unmount itself can trigger writeback flushes (and hence more RPC calls), the trace you are seeing is indeed possible. -- Trond Myklebust Linux NFS client maintainer NetApp Trond.Myklebust+AEA-netapp.com www.netapp.com -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
