transfer lockup connecting to a NetApp/CIFS share

[Kristian Rink]

Binary package hint: samba

Mounting a CIFS share off an IBM N3300 filer (== NetApp FAS 2020), I experienced some file managers, applications, ... to more or less regularly lock up / don't do anything while trying to browse folders. Looking more into this, it seems the problem is more basic. The thing is mounted using cifs:

//192.168.1.252/data on /opt/filer type cifs (rw,mand)

Looking at dmesg, these errors do appear more or less frequently when trying to read off the filer:

[ 3757.049058] CIFS VFS: No response for cmd 50 mid 11642
[ 3763.068762] CIFS VFS: Bad protocol string signature header 4
[ 3763.068788] CIFS VFS: bad smb detected. The Mid=11646
[ 3763.068794] Bad SMB: : dump of 48 bytes of data at 0xf46e8000
[ 3763.068825] 00000040 00000004 00000032 80018800 @ . . . . . . . 2 . . . . . . .
[ 3763.068855] 00000000 00000000 00000000 1e680040 . . . . . . . . . . . . @ . h .
[ 3763.068885] 2d7e0800 0400020a 02000000 00003800 . . ~ - . . . . . . . . . 8 . .
[ 3778.069085] CIFS VFS: No response for cmd 50 mid 11646
[ 3784.087139] CIFS VFS: Bad protocol string signature header 4
[ 3784.087161] CIFS VFS: bad smb detected. The Mid=11650
[ 3784.087165] Bad SMB: : dump of 48 bytes of data at 0xf46e9500
[ 3784.087171] 00000040 00000004 00000032 80018800 @ . . . . . . . 2 . . . . . . .
[ 3784.087195] 00000000 00000000 00000000 1e680040 . . . . . . . . . . . . @ . h .
[ 3784.087202] 2d820800 0400020a 02000000 00003800 . . . - . . . . . . . . . 8 . .
[ 3799.084053] CIFS VFS: No response for cmd 50 mid 11650
[ 3805.102848] CIFS VFS: Bad protocol string signature header 4
[ 3805.102852] CIFS VFS: bad smb detected. The Mid=11654
[ 3805.102873] Bad SMB: : dump of 48 bytes of data at 0xf46e8540
[ 3805.102879] 00000040 00000004 00000032 80018800 @ . . . . . . . 2 . . . . . . .
[ 3805.102903] 00000000 00000000 00000000 1e680040 . . . . . . . . . . . . @ . h .
[ 3805.102909] 2d860800 0400020a 02000000 00003800 . . . - . . . . . . . . . 8 . .
[ 3820.100062] CIFS VFS: No response for cmd 50 mid 11654
[ 3826.119095] CIFS VFS: Bad protocol string signature header 4
[ 3826.119100] CIFS VFS: bad smb detected. The Mid=11658
[ 3826.119120] Bad SMB: : dump of 48 bytes of data at 0xf46e8fc0
[ 3826.119127] 00000040 00000004 00000032 80018800 @ . . . . . . . 2 . . . . . . .
[ 3826.119151] 00000000 00000000 00000000 1e680040 . . . . . . . . . . . . @ . h .
[ 3826.119157] 2d8a0800 0400020a 02000000 00003800 . . . - . . . . . . . . . 8 . .

It happens once in a while copying things off the filer using the shell, and it happens almost reliably when browsing to the share using any visual file manager.

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: smbfs 2:3.4.7~dfsg-1ubuntu2
ProcVersionSignature: Ubuntu 2.6.32-19.28-generic-pae 2.6.32.10+drm33.1
Uname: Linux 2.6.32-19-generic-pae i686
Architecture: i386
CIFSMounts: Error: command ['mount', '|', 'grep', 'cifs'] failed with exit code 1: mount: only root can do that
Date: Thu Apr 8 09:09:58 2010
InstallationMedia: Xubuntu 10.04 "Lucid Lynx" - Alpha i386 (20100224.1)
ProcEnviron:
 PATH=(custom, user)
 LANG=de_DE.utf8
 SHELL=/bin/bash
SambaClientRegression: No
SourcePackage: samba

[Scott Moser (smoser)]

Marking this as 'medium' due to possibly being limited to a given device (IBM N3300 filer). If it occurs more generically then this could be much more severe.
Changing it to linux package.

Do you see this with any other CIFS serving?

[Kristian Rink (kawazu)]

Well, at the very least I fail to reproduce this connecting to a CIFS share provided by a Windows 2003 Server machine, but I'm not using CIFS that much asides connecting to the N3300. Looking at my experiments I did yesterday, this at the very least seems to be the same in 9.04 and 9.10.

[Paul Elliott (omahn)]

I also have this on Lucid. We're attempting to mount a CIFS share from a NetApp 3070 using pam_mount at login. Attempts to login at GDM produce the same kernel errors as provided by OP and result in the login hanging.

[Paul Elliott (omahn)]

Verified that the problem still exists in 2.6.34-020634rc6-generic from the mainline kernel repo.

[John Cooper (choffee)]

Bug #357576 Seems to be similar and they think that it may be fixed in a recent netApp version:

https://bugs.launchpad.net/ubuntu/+source/thunar/+bug/357576

"We got an additional drive bay in our NetApp, and also upgraded software from v7.2.3 to v7.3.1.1 yesterday, and now, the problem with Thunar seems to be gone."

Do you know which NetApp software version you are running?

[John Cooper (choffee)]

Having this problem on OnTap v7.2.4

[Paul Elliott (omahn)]

We have also verified that the issue exists in v7.3.3 and have reported the issue to NetApp.

[John Cooper (choffee)]

Seems to only happen with a cifs mount. When access using nautilus, I assume using gfs, it works okay.

[Paul Elliott (omahn)]

We've just found that disabling extended attributes with either the nouser_xattr mount option or by disabling CONFIG_CIFS_XATTR in the kernel, will allow us to use a NetApp CIFS mount albeit without the extended attribute support. Can anyone else confirm that disabling extended attribute support allows them to use NetApp based CIFS mounts? If so I'll report back to NetApp. (My original close was closed and classed as unsupported unfortunately).

[speeves (speeves)]

The nouser_xattr mount option allows me to browse into subdirectories, but it is still extremely slow. I had hopes, but I'm afraid it isn't the fix... yet.

[penalvch (penalvch)]

Kristian Rink, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ .

If it remains an issue, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.11-rc5

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

If you are unable to test the mainline kernel, please comment as to why specifically you were unable to test it and add the following tags:
kernel-unable-to-test-upstream
kernel-unable-to-test-upstream-VERSION-NUMBER

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

[Kristian Rink (kawazu)]

I am unsure what to do with this one. Haven't tested and can't reproduce this as we don't run this device anymore. Right now, using a "plain" NetApp FAS-2020, OnTap 7.4 and a 3.8.0 kernel off Ubuntu 13.04, this is no longer a problem. As far as I am concerned, this one could be closed.

[penalvch (penalvch)]

Kristian Rink, this bug report is being closed due to your last comment https://bugs.launchpad.net/ubuntu/+source/linux/+bug/557890/comments/13 regarding you don't use the device anymore. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.