On Mon, 28 Nov 2011 14:47:20 -0600 Shirish Pargaonkar <shirishpargaonkar@xxxxxxxxx> wrote: > On Mon, Nov 28, 2011 at 2:32 PM, Jeff Layton <jlayton@xxxxxxxxxx> wrote: > > On Mon, 28 Nov 2011 03:35:22 +0000 > > jr <creature.eternal@xxxxxxxxx> wrote: > > > > > > --------------[snip]---------------- > >> [92841.247667] /build/buildd/linux-3.0.0/fs/cifs/connect.c: CIFS VFS: in > >> cifs_get_tcon as Xid: 54 with uid: 0 > >> [92841.247673] /build/buildd/linux-3.0.0/fs/cifs/transport.c: For > >> smb_command 117 > >> [92841.247677] /build/buildd/linux-3.0.0/fs/cifs/transport.c: Sending > >> smb: total_len 90 > >> [92841.248606] /build/buildd/linux-3.0.0/fs/cifs/connect.c: rfc1002 > >> length 0x27 > >> [92841.248620] /build/buildd/linux-3.0.0/fs/cifs/transport.c: > >> cifs_sync_mid_result: cmd=117 mid=3 state=4 > >> [92841.248625] Status code returned 0xc0000022 NT_STATUS_ACCESS_DENIED > >> [92841.248630] /build/buildd/linux-3.0.0/fs/cifs/netmisc.c: Mapping smb > >> error code 0xc0000022 to POSIX err -13 > >> [92841.248635] /build/buildd/linux-3.0.0/fs/cifs/connect.c: CIFS VFS: > >> leaving cifs_get_tcon (xid = 54) rc = -13 > >> [92841.248639] /build/buildd/linux-3.0.0/fs/cifs/connect.c: CIFS Tcon rc > >> = -13 > > --------------[snip]---------------- > > > > Looks like the tree connect is falling down. Does the user you're > > connecting as have access to the exported share? You may want to check > > the logs on the NAS and see why it's rejecting the tree connect request. > > > > -- > > Jeff Layton <jlayton@xxxxxxxxxx> > > -- > > To unsubscribe from this list: send the line "unsubscribe linux-cifs" in > > the body of a message to majordomo@xxxxxxxxxxxxxxx > > More majordomo info at http://vger.kernel.org/majordomo-info.html > > Ahh yeah, you're correct -- the cause of the failure is here: [92841.251487] /build/buildd/linux-3.0.0/fs/cifs/transport.c: For smb_command 50 [92841.251490] /build/buildd/linux-3.0.0/fs/cifs/transport.c: Sending smb: total_len 108 [92841.252726] /build/buildd/linux-3.0.0/fs/cifs/connect.c: rfc1002 length 0x27 [92841.252731] /build/buildd/linux-3.0.0/fs/cifs/connect.c: invalid transact2 word count [92841.252743] /build/buildd/linux-3.0.0/fs/cifs/transport.c: cifs_sync_mid_result: cmd=50 mid=5 state=4 [92841.252748] Status code returned 0xc0000002 NT_STATUS_NOT_IMPLEMENTED [92841.252752] /build/buildd/linux-3.0.0/fs/cifs/netmisc.c: Mapping smb error code 0xc0000002 to POSIX err -22 [92841.252756] /build/buildd/linux-3.0.0/fs/cifs/cifssmb.c: Send error in GetDFSRefer = -22 and 22 is -EINVAL. This machine is running 3.0? What may be best is to open a bug at bugzilla.samba.org so we can track this. We may need to see a capture of the traffic between the client and server. >From the supplied info: [92841.243787] /build/buildd/linux-3.0.0/fs/cifs/connect.c: Security Mode: 0x3 Capabilities: 0xe3fd TimeAdjust: 0 CAP_DFS does not appear to be set. I also note that we never actually check for SMBFLG2_DFS in the cifs.ko code. It seems like if those bits aren't set, we ought not try to chase DFS referrals at mount time... -- Jeff Layton <jlayton@xxxxxxxxxx> -- To unsubscribe from this list: send the line "unsubscribe linux-cifs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
