I have reported 2 scenarios related to this issue, the second topic being more relevant to your problem. vfs: allow umount to handle mountpoints without revalidating them and NFSERR_STALE on umount with 3.10.0.RC5 kernel Christopher Vogan NFS Development & Test From: Ben Greear <greearb@xxxxxxxxxxxxxxx> To: "Myklebust, Trond" <Trond.Myklebust@xxxxxxxxxx>, Cc: "linux-nfs@xxxxxxxxxxxxxxx" <linux-nfs@xxxxxxxxxxxxxxx> Date: 10/17/2013 01:14 PM Subject: Re: 'umount -f /mnt/foo' fails if server IP is gone. Sent by: linux-nfs-owner@xxxxxxxxxxxxxxx On 10/17/2013 11:05 AM, Myklebust, Trond wrote: > On Thu, 2013-10-17 at 10:35 -0700, Ben Greear wrote: >> On 10/15/2013 11:29 AM, Ben Greear wrote: >>> Is 'umount -f' supposed to always work, even if the file server >>> goes away? >>> >>> I have a user's system that just hangs forever in this case. >>> >>> Could be local changes we have made, but I'm curious about >>> the expected behaviour before I go digging too deep... >> >> Any input on this? I don't mind trying to fix it, but I >> would like to know how it is supposed to work. > > 'umount -f' has always been iffy. It just kills any pending RPC calls > _before_ trying to unmount. Since the unmount itself can trigger > writeback flushes (and hence more RPC calls), the trace you are seeing > is indeed possible. I tried 'umount -f -l', and that also does not work. Any ideas on how to fix this properly? Thanks, Ben -- Ben Greear <greearb@xxxxxxxxxxxxxxx> Candela Technologies Inc http://www.candelatech.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 -- 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
