public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Steve French (smfltc)" <smfltc@us.ibm.com>
To: undisclosed-recipients:;
Subject: Re: Can't mount NAS device
Date: Thu, 29 Mar 2007 16:03:27 -0500	[thread overview]
Message-ID: <460C299F.1020000@us.ibm.com> (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.






                 reply	other threads:[~2007-03-29 21:04 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=460C299F.1020000@us.ibm.com \
    --to=smfltc@us.ibm.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox