cifs mount errors
Subsystems (2)
First, thanks to responders for the help with the "Cannot allocate memory error on mount". The noted change to inode.c did the trick:
- return ERR_PTR(-ENOMEM);
+ return ERR_PTR(rc);
I am also seeing another odd behavior difference between Fedora 7 and Fedora 13. If I try a mount of a share on a particular Windows server I get the following error:
# mount //servername/sharename /mnt -o user=mydom/administrator%mypass mount error(11): Resource temporarily unavailable Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)
It does not matter if I use "dom=mydom,user=administrator%mypass". That also fails. This is odd for several reasons:
1. This does not occur on Fedora 7 systems.
2. Since the server and Linux box are on the same network, the domain name is not needed. Mounting with user=administrator%mypass works fine.
3. If you immediately try the original command a second time on Fedora 13, it succeeds. If you wait about 30 seconds between attempts, it always fails.
Is this a known issue? Are there any tunable timers at play here? What is the cause/intent of the "temporarily unavailable" message.
The log has lines like this with cifsFYI g.t. 0:
CIFS VFS: No response to cmd 115 mid 2 fs/cifs/transport.c: marking request for retry fs/cifs/misc.c: Null buffer passed to cifs_small_buf_release fs/cifs/sess.c: ssetup rc from sendrecv2 is -11 CIFS VFS: Send error in SessSetup = -11
Thanks, Joe H.
A message that is not in the archive (sent off-list or not yet received): 545700.65464.qm-RVHwM+Z+5pGB9c0Qi4KiSs0jms80CZx+QQ4Iyu8u01E@public.gmane.org
Quoted 5 lines · On Mon, 30 Aug 2010 11:41:56 -0700 (PDT) joe hefner…
CIFS VFS: No response to cmd 115 mid 2
fs/cifs/transport.c: marking request for retryfs/cifs/misc.c: Null buffer passed tocifs_small_buf_releasefs/cifs/sess.c: ssetup rc from sendrecv2 is -11 CIFS VFS: Send error in SessSetup = -11
Looks like the server is just not sending a response to the session setup request here. I'd check the server logs -- maybe they have something?
Signature · 1 line
Jeff Layton <[email protected]>