From: Marcus <lists@localguru.de>
To: Jeff Layton <jlayton@samba.org>
Cc: samba@lists.samba.org, linux-cifs@vger.kernel.org
Subject: Re: cifs and Netapp DFS-shares problems
Date: Fri, 10 Dec 2010 16:00:34 +0100 [thread overview]
Message-ID: <1291993234.20912.8.camel@kramer> (raw)
In-Reply-To: <20101210063449.5ab06c5f@tlielax.poochiereds.net>
Hi Jeff,
Am Freitag, den 10.12.2010, 06:34 -0500 schrieb Jeff Layton:
> On Fri, 10 Dec 2010 11:25:46 +0100
> Marcus <lists@localguru.de> wrote:
>
> > Hi,
> >
> > Am Donnerstag, den 09.12.2010, 01:37 +0100 schrieb Marcus:
> > >
> > > 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
> > >
> > > 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)
> > --------------------------
> >
> > 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...
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
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/options/samba
prev parent reply other threads:[~2010-12-10 15:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1291855039.11237.49.camel@kramer>
[not found] ` <1291976746.8971.24.camel@kramer>
2010-12-10 11:34 ` cifs and Netapp DFS-shares problems Jeff Layton
[not found] ` <20101210063449.5ab06c5f-9yPaYZwiELC+kQycOl6kW4xkIHaj4LzF@public.gmane.org>
2010-12-10 11:52 ` [Samba] " Volker Lendecke
2010-12-10 15:17 ` Steve French
2010-12-10 15:00 ` Marcus [this message]
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=1291993234.20912.8.camel@kramer \
--to=lists@localguru.de \
--cc=jlayton@samba.org \
--cc=linux-cifs@vger.kernel.org \
--cc=samba@lists.samba.org \
/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