Bug 1045390

Summary: nfs vers=3 mount => umount and df do not work after system suspend and moved away from..
Product: [Fedora] Fedora Reporter: lejeczek <peljasz>
Component: kernelAssignee: Jeff Layton <jlayton>
Status: CLOSED RAWHIDE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 20CC: bfields, gansalmon, itamar, jlayton, jonathan, kernel-maint, madhu.chinakonda, steved
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-12-20 11:31:10 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description lejeczek 2013-12-20 10:21:53 UTC 
Description of problem:

the network where mount was initially done,
impossible to force umount, df -h just hangs forever, maybe other tools
although system appears to work normally


Version-Release number of selected component (if applicable):

I could not think of where to better place it, maybe not nfs-utils
3.11.10-301.fc20.x86_64

please feel free to request more info
regards

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 1 Jeff Layton 2013-12-20 11:31:10 UTC 
This is pretty much the expected behavior. The default with NFS is a hard mount, which means that the client will retry contacting the server indefinitely to handle requests. You can kill -9 it though (and will need to do so in order to unmount anyway since the df will have hold a reference to the mount).

umount in older kernels has a different issue though. The lookup that the kernel does for the umount can cause it to contact the server too. That's fixed by commit 8033426e6bdb2 that went into v3.12 kernels.

So, the upshot here is that this is expected behavior. But, if you move to a v3.12 kernel, kill off all of the processes accessing the mount (using something like fuser -k), and then use umount -f it should unmount the fs.

I'll go ahead and close this with a resolution of RAWHIDE since the fix is in there and it should be in f20 once v3.12 kernels make their way there. Please reopen if you want to discuss it further.