Mount Error 11 = Resource Temporarily Unavailable
Contents |
for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Ask a Question Ask for Help Receive Real-Time Help Create a Freelance Project cifs resource temporarily unavailable Hire for a Full Time Job Ways to Get Help Expand Search Submit
Samba Mount Error(11) Resource Temporarily Unavailable
Close Search Login Join Today Products BackProducts Gigs Live Careers Vendor Services Groups Website Testing Store Headlines Experts Exchange > Questions > Mount Error 11 = Resource temporily unavailable (CIFS fails to mount Windows network share) Want to Advertise Here? Mount Error 11 = Resource temporily unavailable (CIFS fails to mount Windows network share) Posted on 2015-02-20 Linux Networking Linux 12 Comments 408 Views Last Modified: 2015-02-24 A couple of months I setup mounting a windows file share (Server 2008 R2) on a couple of Centos 5.9 machines using method 4 outlined here - http://wiki.centos.org/TipsAndTricks/WindowsShares. It worked fine for months, but now an issue has come up on a couple of the linux machines. The error is "Mount error 11 = Resource temporarily unavailable". At first I thought it was just because the windows file share it was connected to was restarted for security updates, but restarting or remounting continues to fail with the same error message. No one appears to have said they have changed anything on the linux machines (I very loosely manage them) and nothing has changed with network topology or server (other than the monthly patch Tuesday updates). I've dug through many articles and haven't found anything that works yet. I can still get to file server by manually browsing to it so I don't think it's a networking issue, but related to cifs and stale mount that won't clear. Any ideas? The cifs share in auto mounted /etc/fstab and fails at boot so that would eliminate other shares causing the error. 0 Question by:futureman0 Facebook Twitter LinkedIn Google 12 Comments LVL 9 Overall: Level 9 Linux 2 Message Expert Comment by:Rob_Jeffrey2015-02-20 You may have stale mounts - try clearing all CIFS mounts with: umount -a -f cifs Then re-mount everything in
Thu, 27 Dec 2007 13:12:01 UTC Severity: important Found in version 2.6.18-1 Fixed in version 2.6.22-1 Done: Steve Langasek
"mount error 11" Date: Wed, 9 Jul 2008 13:59:51 -0500 I cannot https://www.redhat.com/archives/redhat-sysadmin-list/2008-July/msg00012.html mount a Windows2003 Enterprise share on my Redhat 5.1 server. Nearly every time, the mount fails, but the few times it has worked https://bugzilla.samba.org/show_bug.cgi?id=3857 I've done nothing differently. My /etc/fstab entry: > \\192.168.35.11\Backups /mnt/backups cifs credentials=/root/.cred,noauto,gid=500,uid=500,file_mode=0777,dir_mode=0777,rw 0 0 Sometimes the mounting works but usually is does resource temporarily not, giving the error: > [root rhel51 ~]# mount /mnt/backups/ > mount error 11 = Resource temporarily unavailable > Refer to the mount.cifs(8) manual page (e.g.man mount.cifs) which clarifies nothing for me. If I change the fstab entry to 'smbfs', I get this error: > resource temporarily unavailable [root rhel51 ~]# mount /mnt/backups/ > mount: unknown filesystem type 'smbfs' I am not sure if these are related or not, from /var/log/samba/smbd.log: > [2008/07/09 13:24:38, 0] auth/auth_util.c:create_builtin_administrators(792) > create_builtin_administrators: Failed to create Administrators > [2008/07/09 13:24:38, 0] auth/auth_util.c:create_builtin_users(758) > create_builtin_users: Failed to create Users > [2008/07/09 13:27:49, 0] auth/auth_util.c:create_builtin_administrators(792) > create_builtin_administrators: Failed to create Administrators > [2008/07/09 13:27:49, 0] auth/auth_util.c:create_builtin_users(758) > create_builtin_users: Failed to create Users ...and from /var/log/samba/wb-NETBIOSNAME.log > [2008/07/09 13:27:49, 0] nsswitch/winbindd_passdb.c:sid_to_name(130) > Possible deadlock: Trying to lookup SID S-1-1-0 with passdb backend > [2008/07/09 13:27:49, 0] nsswitch/winbindd_passdb.c:sid_to_name(130) > Possible deadlock: Trying to lookup SID S-1-5-2 with passdb backend Can anyone help me with this? The kernel is: > 2.6.18-53.1.6.el5 #1 SMP .... x86_64 x86_64 x86_64 GNU/Linux [Date Prev][Date Next] [Thread Prev][Thread Next] [Thread Index] [Date Index] [Author Index]
[x] First Last Prev Next This bug is not in your last search results. Bug3857 - mount error 11 = Resource temporarily unavailable Summary: mount error 11 = Resource temporarily unavailable Status: RESOLVED FIXED Product: CifsVFS Classification: Unclassified Component: user space tools Version: 2.6 Hardware: x86 Linux Importance: P3 normal TargetMilestone: --- Assigned To: Steve French QA Contact: URL: Keywords: Depends on: Blocks: Show dependency tree /graph Reported: 2006-06-26 02:42 UTC by stefan matthäus Modified: 2009-08-24 18:07 UTC (History) CC List: 1 user (show) shirishp See Also: Attachments Reestablish cifs session for a mount after a disconnection (746 bytes, patch) 2007-09-26 09:49 UTC, Matthieu Lochegnies no flags Details View All Add an attachment (proposed patch, testcase, etc.) Note You need to log in before you can comment on or make changes to this bug. Description stefan matthäus 2006-06-26 02:42:31 UTC I am trying to mount some cifs shares from a Windows Server 2003 domain server to a Debian Linux machine (sarge 3.1 with all available updates). I am getting often problems to mount the shares, but sometimes it is successfull. The Debian system uses a kernel 2.6.8-2 686-SMP, now updatet to 2.6.8-3-SMP. The problem is that if I try to mount a Windows share, then I get often the following error message: larch:/mnt/shares# mount share4/ mount error 11 = Resource temporarily unavailable Refer to the mount.cifs(8) manual page (e.g.man mount.cifs) (I am not sure if the problematic Component is kernel fs or userspace tool.) When I retry the command one or two times more, it is suddenly successfull, without changing anything else. What I also could observe, is that it mostly mounts 3 shares successfully, and then the 4th and 5th do not. It does not care which three shares I mount first, always the 4th fails. That also happens at boot time, as these shares are written in the fstab, so 2 of 5 shares were not mounted successfully at boot up. For your reference, here is a short example protocol of my doing: larch:/mnt/shares# ll total 8 drwxrwx--- 1 user user 0 Jun 23 15:07 share1 drwxrwx--- 1 user user 0 Jun 22 12:00 share2 drwxrwx--- 1 user user 0 Jun 21 10:50 share3 drwxr-xr-x 2 root root 4096 Jun 21 13:43 share4 drwxr-xr-x 2 root root 4096 Jun 21 13:44 share5 (so share 1-3 have been mounted, 4&5 not) larch:/mnt/shares# mount share4/ mount err