Skip to contentSkip to conversation

cifs and Netapp DFS-shares problems

DISCUSSION Jeff Layton 4 participants 4 messages Dec 10, 2010 3 messages not in the archive

Subsystems (2)
lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): 1291855039.11237.49.camel@kramer

A message that is not in the archive (sent off-list or not yet received): 1291976746.8971.24.camel@kramer

#2 lore raw
Quoted 66 lines · On Fri, 10 Dec 2010 11:25:46 +0100 Marcus <[email protected]> wrote:

Hi,

Am Donnerstag, den 09.12.2010, 01:37 +0100 schrieb Marcus:

Quoted 5 lines

are there any known issues with cifs and DFS-shares on Netapp file servers? We have a Netapp file sever with DFS on the user's home shares. The home shares can successfully mounted with

Quoted 7 lines

mount -t cifs //sever/home/username /mnt/ -o user=username,domain=AD

but the connection hangs in the moment a directory listing is started. The strange thing is that only shares with activated DFS show this problem. I'm not maintaining the Netapp file server therefore a can't post more information about that system. On client side I'm using Ubuntu LTS 10.04.1.

This error only comes up, if DFS is activated on a share on the NetApp Server. Here is a kernel log:

Dec 10 11:10:37 lebowski kernel: [ 3586.471662] Bad SMB: : dump of 48
bytes of data at 0xe44e5c00
Dec 10 11:10:37 lebowski kernel: [ 3586.471675]  0000009a 424d53ff
00000032 80018800 . . . . ÿ S M B 2 . . . . . . .
Dec 10 11:10:37 lebowski kernel: [ 3586.471688]  00000000 00000000
00000000 26420040 . . . . . . . . . . . . @ . B &
Dec 10 11:10:37 lebowski kernel: [ 3586.471701]  001a0800 7000020a
02000000 00003800 . . . . . . . p . . . . . 8 . .
Dec 10 11:11:03 lebowski kernel: [ 3612.832108]  CIFS VFS: server not
responding
Dec 10 11:11:03 lebowski kernel: [ 3612.832125]  CIFS VFS: No response
for cmd 50 mid 26
Dec 10 11:11:05 lebowski kernel: [ 3614.656937]  CIFS VFS: RFC1001 size
154 bigger than SMB for Mid=30
Dec 10 11:11:05 lebowski kernel: [ 3614.656953] Bad SMB: : dump of 48
bytes of data at 0xe44e5c00
Dec 10 11:11:05 lebowski kernel: [ 3614.656967]  0000009a 424d53ff
00000032 80018800 . . . . ÿ S M B 2 . . . . . . .
Dec 10 11:11:05 lebowski kernel: [ 3614.656979]  00000000 00000000
00000000 26420040 . . . . . . . . . . . . @ . B &
Dec 10 11:11:05 lebowski kernel: [ 3614.656994]  001e0800 7000020a
02000000 00003800 . . . . . . . p . . . . . 8 . .
Dec 10 11:11:33 lebowski kernel: [ 3642.832284]  CIFS VFS: server not
responding
Dec 10 11:11:33 lebowski kernel: [ 3642.832299]  CIFS VFS: No response
for cmd 50 mid 30
Dec 10 11:11:40 lebowski kernel: [ 3649.895000]  CIFS VFS: RFC1001 size
154 bigger than SMB for Mid=34
Dec 10 11:11:40 lebowski kernel: [ 3649.895017] Bad SMB: : dump of 48
bytes of data at 0xe44e5c00
Dec 10 11:11:40 lebowski kernel: [ 3649.895030]  0000009a 424d53ff
00000032 80018800 . . . . ÿ S M B 2 . . . . . . .
Dec 10 11:11:40 lebowski kernel: [ 3649.895043]  00000000 00000000
00000000 26420040 . . . . . . . . . . . . @ . B &
Dec 10 11:11:40 lebowski kernel: [ 3649.895056]  00220800 7000020a

02000000 00003800 . . " . . . . p . . . . . 8 . .
--------------------------

umounting is impossible and gives the following error:

--------------------------
unmount error 16 = Device or resource busy
Refer to the umount.cifs(8) manual page (man 8 umount.cifs) unmount error 16 = Device or resource busy
Refer to the umount.cifs(8) manual page (man 8 umount.cifs)
--------------------------

Quoted 6 lines

Any ideas? Seems to be an error of the NetApp Fileserver acting not RFC conform.

Is this the right list to discuss or should I post on linux-cifs-client list?

(cc'ing linux-cifs mailing list)

Probably because the ls is hung and is holding references to the mount...

I've successfully tested against netapp's CIFS implementation in the past, but there are significant bugs in it. The errors you're seeing look like an alignment problem of some sort -- i.e. the server is sending packets that have incorrect length fields in them. This isn't the first such problem I've seen with OnTap.

You're welcome to open a bug at bugzilla.samba.org, cc me, and I'll take a look when I have time. Gathering wire captures during one of these events and attaching them to the bug would help to track down the problem. It's likely to be Netapp's bug however...

Signature · 4 lines
Jeff Layton <[email protected]>
-- 
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/options/samba

A message that is not in the archive (sent off-list or not yet received): 20101210063449.5ab06c5f-9yPaYZwiELC+kQycOl6kW4xkIHaj4LzF@public.gmane.org

#4 lore raw
Quoted 4 lines · Jeff Layton

You're welcome to open a bug at bugzilla.samba.org, cc me, and I'll take a look when I have time. Gathering wire captures during one of these events and attaching them to the bug would help to track down the problem. It's likely to be Netapp's bug however...

NetApp explicitly refuses to fix anything that is outside their supported client matrix. I've heard that from NetApp reps responsible for my customers. cifsfs is outside that matrix. NetApp's fix is to tell people to use NFS when coming from Linux.

Volker

#5 lore raw
In reply to a message not in the archive
Quoted 18 lines · Jeff Layton
Quoted 6 lines · On Fri, 10 Dec 2010 11:25:46 +0100 Marcus…

Any ideas? Seems to be an error of the NetApp Fileserver acting not RFC conform.

Is this the right list to discuss or should I post on linux-cifs-client list?

(cc'ing linux-cifs mailing list)

Probably because the ls is hung and is holding references to the mount...

I've successfully tested against netapp's CIFS implementation in the past, but there are significant bugs in it. The errors you're seeing look like an alignment problem of some sort -- i.e. the server is sending packets that have incorrect length fields in them. This isn't the first such problem I've seen with OnTap.

Quoted 4 lines

You're welcome to open a bug at bugzilla.samba.org, cc me, and I'll take a look when I have time. Gathering wire captures during one of these events and attaching them to the bug would help to track down the problem. It's likely to be Netapp's bug however...

We have worked around a few similar sounding server bugs in the past, but have to be careful that we don't introduce potential buffer overruns or security problems (the Linux cifs client parses frames more carefully than some other clients to reduce the chance of going beyond the end of frames).

Signature · 3 lines
Thanks,

Steve
#6 lore raw
In reply to Jeff Layton

Hi Jeff,

Am Freitag, den 10.12.2010, 06:34 -0500 schrieb Jeff Layton:

Quoted 85 lines
Quoted 66 lines · On Fri, 10 Dec 2010 11:25:46 +0100 Marcus <[email protected]> wrote:

Hi,

Am Donnerstag, den 09.12.2010, 01:37 +0100 schrieb Marcus:

Quoted 5 lines

are there any known issues with cifs and DFS-shares on Netapp file servers? We have a Netapp file sever with DFS on the user's home shares. The home shares can successfully mounted with

Quoted 7 lines

mount -t cifs //sever/home/username /mnt/ -o user=username,domain=AD

but the connection hangs in the moment a directory listing is started. The strange thing is that only shares with activated DFS show this problem. I'm not maintaining the Netapp file server therefore a can't post more information about that system. On client side I'm using Ubuntu LTS 10.04.1.

This error only comes up, if DFS is activated on a share on the NetApp Server. Here is a kernel log:

Dec 10 11:10:37 lebowski kernel: [ 3586.471662] Bad SMB: : dump of 48
bytes of data at 0xe44e5c00
Dec 10 11:10:37 lebowski kernel: [ 3586.471675]  0000009a 424d53ff
00000032 80018800 . . . . ÿ S M B 2 . . . . . . .
Dec 10 11:10:37 lebowski kernel: [ 3586.471688]  00000000 00000000
00000000 26420040 . . . . . . . . . . . . @ . B &
Dec 10 11:10:37 lebowski kernel: [ 3586.471701]  001a0800 7000020a
02000000 00003800 . . . . . . . p . . . . . 8 . .
Dec 10 11:11:03 lebowski kernel: [ 3612.832108]  CIFS VFS: server not
responding
Dec 10 11:11:03 lebowski kernel: [ 3612.832125]  CIFS VFS: No response
for cmd 50 mid 26
Dec 10 11:11:05 lebowski kernel: [ 3614.656937]  CIFS VFS: RFC1001 size
154 bigger than SMB for Mid=30
Dec 10 11:11:05 lebowski kernel: [ 3614.656953] Bad SMB: : dump of 48
bytes of data at 0xe44e5c00
Dec 10 11:11:05 lebowski kernel: [ 3614.656967]  0000009a 424d53ff
00000032 80018800 . . . . ÿ S M B 2 . . . . . . .
Dec 10 11:11:05 lebowski kernel: [ 3614.656979]  00000000 00000000
00000000 26420040 . . . . . . . . . . . . @ . B &
Dec 10 11:11:05 lebowski kernel: [ 3614.656994]  001e0800 7000020a
02000000 00003800 . . . . . . . p . . . . . 8 . .
Dec 10 11:11:33 lebowski kernel: [ 3642.832284]  CIFS VFS: server not
responding
Dec 10 11:11:33 lebowski kernel: [ 3642.832299]  CIFS VFS: No response
for cmd 50 mid 30
Dec 10 11:11:40 lebowski kernel: [ 3649.895000]  CIFS VFS: RFC1001 size
154 bigger than SMB for Mid=34
Dec 10 11:11:40 lebowski kernel: [ 3649.895017] Bad SMB: : dump of 48
bytes of data at 0xe44e5c00
Dec 10 11:11:40 lebowski kernel: [ 3649.895030]  0000009a 424d53ff
00000032 80018800 . . . . ÿ S M B 2 . . . . . . .
Dec 10 11:11:40 lebowski kernel: [ 3649.895043]  00000000 00000000
00000000 26420040 . . . . . . . . . . . . @ . B &
Dec 10 11:11:40 lebowski kernel: [ 3649.895056]  00220800 7000020a

02000000 00003800 . . " . . . . p . . . . . 8 . .
--------------------------

umounting is impossible and gives the following error:

--------------------------
unmount error 16 = Device or resource busy
Refer to the umount.cifs(8) manual page (man 8 umount.cifs) unmount error 16 = Device or resource busy
Refer to the umount.cifs(8) manual page (man 8 umount.cifs)
--------------------------

Quoted 6 lines

Any ideas? Seems to be an error of the NetApp Fileserver acting not RFC conform.

Is this the right list to discuss or should I post on linux-cifs-client list?

(cc'ing linux-cifs mailing list)

Probably because the ls is hung and is holding references to the mount...

I've successfully tested against netapp's CIFS implementation in the past, but there are significant bugs in it. The errors you're seeing look like an alignment problem of some sort -- i.e. the server is sending packets that have incorrect length fields in them. This isn't the first such problem I've seen with OnTap.

Quoted 4 lines

You're welcome to open a bug at bugzilla.samba.org, cc me, and I'll take a look when I have time. Gathering wire captures during one of these events and attaching them to the bug would help to track down the problem. It's likely to be Netapp's bug however...

Thanks for helping. I've posted a bug [1] with a tcpdump.

Have a nice weekend,
Marcus

[1] https://bugzilla.samba.org/show_bug.cgi?id=7860

Signature · 2 lines
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/options/samba