[linux-cifs-client] Re: Can't mount NAS device

[Steve French (smfltc)]

Dominik Strasser wrote:

> Steve French (smfltc) schrieb:
>
> Hi Steve,
>
>>> I've sent the message below some months ago, but haven't received 
>>> any answer. Was the question inappropriate ? Wrong list ? Can 
>>> somebody here on the list help me ?
>>>
>>> Thanks
>>>
>>> Can you help? I tried to do some experiments playing with the 
>>> command length which seems to be off, but apart from hangs I didn't 
>>> produce anything usable.
>>>  
>>>
>> I don't see the actual error in the log (my guess is that you turned 
>> /proc/fs/cifs/cifsFYI to 1 instead of 7 so
>> we don't see some of the higher level errors).   Looks like the 
>> server is an older version of Samba
>> that supports the early CIFS Unix Extensions but does not support 
>> SetFSInfo (for
>> negotiating unix capabilities).    After the server fails the 
>> SetFSInfo I see a read_inode so it
>> looks like this older cifs code, as with current cifs code, can 
>> handle the server returning an error on this.
>> Basically it looks like mount succeeded if it made it this far.
>>
>> Perhaps the read_inode on the root directory of the mount succeeds 
>> but the server returned that it is not
>> a directory?
>>
>> You can force a different path to this type of server by turning off 
>> the Unix/Linux extensions before mount:
>>
>>    "echo 0 > /proc/fs/cifs/LinuxExtensionsEnabled"
>>
>> that will force the Linux CIFS client to treat the server more like 
>> Windows (and try older levels
>> of the same calls - but it will mean that you will not get the owner 
>> and mode
>> information of the files from the server but will get default values 
>> for those)
>
> Thank you very much, this one did the trick!
> Do you want me to send more info, is there anything that you want to 
> track down ?
>
> Regards
>
> Dominik
>
>> _______________________________________________
>> linux-cifs-client mailing list
>> linux-cifs-client at lists.samba.org
>> https://lists.samba.org/mailman/listinfo/linux-cifs-client
>>
>>
>
>
There is nothing more to do if your level of cifs code does not work, 
but more current cifs code does (as there have been some
dramatic improvements in the Linux/Unix protocol extensions).   If you 
have not tried a more current cifs module.   e.g.
     http://pserver.samba.org/samba/ftp/cifs-cvs/cifs-1.48.tar.gz
(you would need to be familiar with the simple steps required to build 
and load kernel module), I would like you to try
that newer version of cifs just to make sure we are not looking at an 
already fixed problem.

For the older cifs code which you are running which fails, it might be 
helpful if you did:

"dmesg -c" to clear the message log
"echo 7 > /proc/fs/cifs/cifsFYI" to set maximum logging for cifs
"mount -t cifs ..." attempt the cifs mount as before
If it fails send the dmesg output - I think that might return a little 
more data - I am looking for what is returned on the lookup/stat of the 
root inode.