public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
* Re: Can't mount NAS device
@ 2007-03-29 21:03 Steve French (smfltc)
  0 siblings, 0 replies; only message in thread
From: Steve French (smfltc) @ 2007-03-29 21:03 UTC (permalink / raw)


strace did show something useful
	mount(...) = -1 ENOTDIR (Not a directory)

and then that led me to spotting the obvious bug which is
on your NAS device (server).  The server is returning a
malformed (illegal) response.

The Linux cifs client was getting a 22 byte response to a level 0x200
(FILE_UNIX_BASIC_INFO) request that is supposed to be 100 bytes.

Basically connecting the mount to the server succeeded but 
the stat of "." (the top directory in the mount) failed 
since it is not recognized as a directory.

When you disable the Unix Extensions on the client ie
	echo 0 > /proc/fs/cifs/LinuxExtensionsEnabled
you bypass the bug on the server, because the response to
the call which is malformed is not issued (and an older
infolevel is requested).

If your server vendor produces a fix let me know and I can add
the information about the required level of server to 
the Linux cifs client "how-to" / user's guide.






^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2007-03-29 21:04 UTC | newest]

Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2007-03-29 21:03 Can't mount NAS device Steve French (smfltc)

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox