Bug 465811
Summary: | Can't unmount a samba share (cifs) | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Simon Andrews <simon.andrews> |
Component: | kernel | Assignee: | Jeff Layton <jlayton> |
Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 9 | CC: | gdeschner, jlayton, kernel-maint, kwright, ssorce, steved |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2008-10-20 16:11:35 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Simon Andrews
2008-10-06 15:03:07 UTC
I found the following in /var/log/messages which are probably much more informative about the underlying cause of this error; Oct 6 14:18:25 bilin1 kernel: Status code returned 0xc000006d NT_STATUS_LOGON_FAILURE Oct 6 14:18:25 bilin1 kernel: CIFS VFS: Send error in SessSetup = -13 Oct 6 14:18:25 bilin1 kernel: CIFS VFS: cifs_mount failed w/return code = -13 Oct 6 14:18:30 bilin1 kernel: Status code returned 0xc000006d NT_STATUS_LOGON_FAILURE Oct 6 14:18:30 bilin1 kernel: CIFS VFS: Send error in SessSetup = -13 Oct 6 14:18:30 bilin1 kernel: CIFS VFS: cifs_mount failed w/return code = -13 Oct 6 14:21:13 bilin1 kernel: CIFS VFS: RFC1001 size 35 bigger than SMB for Mid=5819 Oct 6 14:21:40 bilin1 kernel: CIFS VFS: server not responding Oct 6 14:21:40 bilin1 kernel: CIFS VFS: No response to cmd 116 mid 5819 This seem a cifs.ko kernel module issue, reassigning. I'm fairly certain this is actually an ontap bug. Someone opened a case for the same problem a while back and I closed it, but I can't seem to find it at the moment. Some versions of OnTap send malformed SMBLogoff replies. The umount will eventually work, but it can take a few minutes before the call times out. Aside from the long timeout on umounts, the bug is fairly harmless. There's not much we can do about this other than to suggest filing a bug with Netapp. Hopefully more recent ontap versions have fixed this. I'm going to go ahead and close this as NOTABUG. Please reopen if you have questions... Reported to me by krishnoid If you unmount the share twice in the background: $ sudo umount /mnt/share & $ sudo umount /mnt/share & this will unmount the share immediately. |