[linux-cifs-client] Can mount from one box, but not another

Shirish S Pargaonkar shirishp at us.ibm.com
Thu Nov 9 15:41:52 GMT 2006







Laker Netman <laker_netman at yahoo.com> wrote on 11/08/2006 03:20:06 PM:

>
> Sorry about top-posting earlier, see below.

> ----- Original Message ----
> From: Shirish S Pargaonkar <shirishp at us.ibm.com>
> To: Laker Netman <laker_netman at yahoo.com>
> Cc: linux-cifs-client at lists.samba.org; linux-cifs-client-
> bounces+shirishp=us.ibm.com at lists.samba.org
> Sent: Wednesday, November 8, 2006 1:16:15 PM
> Subject: Re: [linux-cifs-client] Can mount from one box, but not another

> linux-cifs-client-bounces+shirishp=us.ibm.com at lists.samba.org wrote
> on 11/08/2006 11:07:09 AM:
>
> > Output from WORKING box:
> >
> >  fs/cifs/cifsfs.c: Devname: //itcdrw/c$ flags: 64
> >  fs/cifs/connect.c: CIFS VFS: in cifs_mount as Xid: 595 with uid: 0
> >  fs/cifs/connect.c: Username: Administrator
> >  fs/cifs/connect.c: UNC: \\itcdrw\c$ ip: 192.168.12.209
> >  fs/cifs/connect.c: Socket created
> >  fs/cifs/connect.c: sndbuf 16384 rcvbuf 87380 rcvtimeo 0x7fffffff
> >  fs/cifs/connect.c: Demultiplex PID: 25100
> >  fs/cifs/connect.c: Existing smb sess not found
> >  fs/cifs/transport.c: For smb_command 114
> >  fs/cifs/transport.c: Sending smb of length 47
> >  fs/cifs/connect.c: rfc1002 length 0x7f)
> >  fs/cifs/connect.c: Security Mode: 0x3 Capabilities: 0xe3fd Time Zone:
360
> >  fs/cifs/connect.c: In sesssetup
> >  fs/cifs/transport.c: For smb_command 115
> >  fs/cifs/transport.c: Sending smb of length 262
> >  fs/cifs/connect.c: rfc1002 length 0x97)
> >  fs/cifs/connect.c: UID = 2048
> >  fs/cifs/connect.c: CIFS Session Established successfully
> >  fs/cifs/connect.c: file mode: 0x7f7  dir mode: 0x1ff
> >  fs/cifs/transport.c: For smb_command 117
> >  fs/cifs/transport.c: Sending smb of length 74
> >  fs/cifs/connect.c: rfc1002 length 0x42)
> >  fs/cifs/connect.c: Tcon flags: 0x1
> >  fs/cifs/connect.c: CIFS Tcon rc = 0
> >  fs/cifs/cifssmb.c: In QFSDeviceInfo
> >  fs/cifs/transport.c: For smb_command 50
> >  fs/cifs/transport.c: Sending smb of length 68
> >  fs/cifs/connect.c: rfc1002 length 0x44)
> >  fs/cifs/cifssmb.c: In QFSAttributeInfo
> >  fs/cifs/transport.c: For smb_command 50
> >  fs/cifs/transport.c: Sending smb of length 68
> >  fs/cifs/connect.c: rfc1002 length 0x50)
> >  fs/cifs/connect.c: CIFS VFS: leaving cifs_mount (xid = 595) rc = 0
> >  fs/cifs/inode.c: CIFS VFS: in cifs_read_inode as Xid: 596 with uid: 0
> >  fs/cifs/inode.c: Getting info on
> >  fs/cifs/transport.c: For smb_command 50
> >  fs/cifs/transport.c: Sending smb of length 74
> >  fs/cifs/connect.c: rfc1002 length 0x8a)
> >  fs/cifs/inode.c: Old time 0
> >  fs/cifs/inode.c: New time 774714125
> >  fs/cifs/inode.c: Directory inode
> >  fs/cifs/inode.c: CIFS VFS: in cifs_revalidate as Xid: 597 with uid: 68
> >  fs/cifs/inode.c: Revalidate:  inode 0xcc17d99c count 1 dentry:
> > 0xc30f7490 d_time 774706528 jiffies 774714126
> >  fs/cifs/inode.c: CIFS VFS: leaving cifs_revalidate (xid = 597) rc = 0
> >
> > Output from NON-WORKING box:
> >
> >  fs/cifs/cifsfs.c: Devname: //itcdrw/c$ flags: 64
> >  fs/cifs/connect.c: CIFS VFS: in cifs_mount as Xid: 69 with uid: 0
> >  fs/cifs/connect.c: Username: Administrator
> >  fs/cifs/connect.c: UNC: \\itcdrw\c$ ip: 192.168.12.209
> >  fs/cifs/connect.c: Socket created
> >  fs/cifs/connect.c: sndbuf 16384 rcvbuf 87380 rcvtimeo 0x7fffffff
> >  fs/cifs/connect.c: Demultiplex PID: 3613
> >  fs/cifs/connect.c: Existing smb sess not found
> >  fs/cifs/cifssmb.c: secFlags 0x7
> >  fs/cifs/transport.c: For smb_command 114
> >  fs/cifs/transport.c: Sending smb of length 67
> >  fs/cifs/connect.c: rfc1002 length 0x7f)
> >  fs/cifs/cifssmb.c: Dialect: 1
> >  fs/cifs/cifssmb.c: negprot rc 0
> >  fs/cifs/connect.c: Security Mode: 0x3 Capabilities: 0xe3fd Time Zone:
360
> >  fs/cifs/sess.c: sess setup type 1
> >  fs/cifs/transport.c: For smb_command 115
> >  fs/cifs/transport.c: Sending smb:  total_len 288
> >  fs/cifs/connect.c: rfc1002 length 0x27)
> >  fs/cifs/netmisc.c:  !!Mapping smb error code 5 to POSIX err -13 !!
> >  fs/cifs/misc.c: Null buffer passed to cifs_small_buf_release
> >  fs/cifs/sess.c: ssetup rc from sendrecv2 is -13
> >  fs/cifs/sess.c: ssetup freeing small buf d1358200
> >  CIFS VFS: Send error in SessSetup = -13
> >  fs/cifs/connect.c: No session or bad tcon
> >  fs/cifs/connect.c: CIFS VFS: leaving cifs_mount (xid = 69) rc = -13
> >  CIFS VFS: cifs_mount failed w/return code = -13
> >
> > Also, I have tried this with "user=X,password=Y" to insure no typoes
> > in the password :)
>
> > ----- Original Message ----
> > From: Shirish S Pargaonkar <shirishp at us.ibm.com>
> > To: Laker Netman <laker_netman at yahoo.com>
> > Cc: linux-cifs-client at lists.samba.org
> > Sent: Wednesday, November 8, 2006 9:56:12 AM
> > Subject: Re: [linux-cifs-client] Can mount from one box, but not
another
>
> > linux-cifs-client-bounces+shirishp=us.ibm.com at lists.samba.org wrote
> > on 11/08/2006 09:03:10 AM:
> >
> > > Hi all.
> > >
> > > The short version is I have two FC5 boxes connecting to a Windows
> > > 2000 workstation's administrative shares on C$ and D$.  "Box 1" was
> > > installed with FC5 from scratch (and updates nightly with Yum).  It
> > > connects without issue to the W2K workstation in question, as
> > > Administrator.  The second FC5 box was upgraded from FC4.
> > > Previously at FC4 this box also connected without issue to the same
> > > W2K box, again as Administrator.  After the upgrade to FC5 all is
> > > get in "Box 2"s kernel log is:
> > >  CIFS VFS: Send error in SessSetup = -13
> > >  CIFS VFS: cifs_mount failed w/return code = -13
> > >
> > > Googling has not turned up any valuable info on this error.
> > >
> > > Suggestions as to what to reinstall/reconfigure or what to post for
> > > additional clues are appreciated.
> > >
> > > TIA,
> > > Laker
> >
> > Can you issue these commands on the FC Linux box  echo 1 >
> > /proc/fs/cifs/cifsFYI; dmesg -c
> > and then repeat the error case and send the dmesg output?
> > You can also generate an ethereal trace on either windows box or FC
> > Linux box and send that file.
> > I get the same error when I send incorrect password.  -13 is error
> > code EACCESS (permission denied).
> >
> > Regards,
> >
> > Shirish
> >
>
> This helps.  But what would help additionally be similar output of
> the dmesg command after you issue
> echo 1 > /proc/fs/cifs/traceSMB; dmesg -c
> You can only send the output from the error case client.
> BTW, are versions of cifs.ko different on both the linux clients?
> Not that it matters, just for my information.
>
> Regards,
>
> Shirish
>
>
>  fs/cifs/cifsfs.c: Devname: //itcdrw/c$ flags: 64
>  fs/cifs/connect.c: CIFS VFS: in cifs_mount as Xid: 113 with uid: 0
>  fs/cifs/connect.c: Username: Administrator
>  fs/cifs/connect.c: UNC: \\itcdrw\c$ ip: 192.168.12.209
>  fs/cifs/connect.c: Socket created
>  fs/cifs/connect.c: sndbuf 16384 rcvbuf 87380 rcvtimeo 0x7fffffff
>  fs/cifs/connect.c: Demultiplex PID: 4909
>  fs/cifs/connect.c: Existing smb sess not found
>  fs/cifs/cifssmb.c: secFlags 0x7
>  fs/cifs/transport.c: For smb_command 114
>  fs/cifs/transport.c: Sending smb of length 67
>  fs/cifs/connect.c: rfc1002 length 0x7f)
>  fs/cifs/cifssmb.c: Dialect: 1
>  fs/cifs/cifssmb.c: negprot rc 0
>  fs/cifs/connect.c: Security Mode: 0x3 Capabilities: 0xe3fd Time Zone:
360
>  fs/cifs/sess.c: sess setup type 1
>  fs/cifs/transport.c: For smb_command 115
>  fs/cifs/transport.c: Sending smb:  total_len 288
>  fs/cifs/connect.c: rfc1002 length 0x27)
>  fs/cifs/netmisc.c:  !!Mapping smb error code 5 to POSIX err -13 !!
>  fs/cifs/misc.c: Null buffer passed to cifs_small_buf_release
>  fs/cifs/sess.c: ssetup rc from sendrecv2 is -13
>  fs/cifs/sess.c: ssetup freeing small buf d1358740
>  CIFS VFS: Send error in SessSetup = -13
>  fs/cifs/connect.c: No session or bad tcon
>  fs/cifs/connect.c: CIFS VFS: leaving cifs_mount (xid = 113) rc = -13
>  CIFS VFS: cifs_mount failed w/return code = -13
>
> AND, I may have found a portion of the issue, but not a solution.
> The working box is running kernel 2.6.17-1.2187_FC5 and the NON-
> working box is running 2.6.18-1.220.fc5
> The working box cifs.ko is  261008 bytes, dated September 11th, the
> NON-working cifs.ko is 217809 bytes dated October 14th.
>
> So, can I get back to the previous CIFS ko with the current kernel?
>
> Laker

What does command   modinfo cifs   say on either of the boxes?
You can try running version of cifs.ko on the working box on the
non-working box
and see if that works. But would be nice if you can send the dmesg output
after echo 1 > /proc/fs/cifs/traceSMB, clearing the dmesg, and then running
the test case
that generates new dmesg data.

Regards,

Shirish
-------------- next part --------------
HTML attachment scrubbed and removed


More information about the linux-cifs-client mailing list