search for: cifs_get_inode_info

...The kernel output after enabling extended debugging: dir.c: CIFS VFS: in cifs_lookup as Xid: 108299 with uid: 0 dir.c: parent inode = 0xe754c200 name is: bla and dentry = 0xef5317a0 dir.c: len 4 dir.c: NULL inode in lookup dir.c: Full path: \bla inode = 0x00000000 inode.c: CIFS VFS: in cifs_get_inode_info as Xid: 108300 with uid: 0 inode.c: Getting info on \bla cifssmb.c: In QPathInfo path \bla transport.c: For smb_command 50 transport.c: Sending smb of length 82 connect.c: Peek length rcvd: 36 with smb length: 39 connect.c: Mid 0xc7a8 matched - waking up transport.c: Unexpected signature re...

BUG: soft lockup detected on CPU#0! Pid: 2213, comm: smbiod EIP: 0061:[<f4990f2e>] CPU: 0 EIP is at smbiod+0x116/0x16d [smbfs] EFLAGS: 00000246 Tainted: GF (2.6.16-xen-automount #1) EAX: 00000000 EBX: f4996400 ECX: f2c99f68 EDX: f2c98000 ESI: f2c98000 EDI: c06f5780 EBP: f2c99fb8 DS: 007b ES: 007b CR0: 8005003b CR2: b7f77000 CR3: 326e2000 CR4: 00000640

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, We have `some` problems related to the samba daemon, or possibly with the Linux kernel CIFS filesystem. We have 2 server (for this example): - - Storage Server, running Samba 3.0.28a on Ubuntu Linux (Samba version 3.0.28a-1ubuntu4.4) with ldap authentication. - - Client, running Linux 2.6.24 as a XEN domU. This server mounts on demand user

...ponse buffer Oct 18 11:35:42 dlib2 last message repeated 2 times Oct 18 11:35:42 dlib2 kernel: CIFS VFS: Error -104 sending data on socket to server. Oct 18 11:35:42 dlib2 kernel: CIFS VFS: Error -32 sending data on socket to server. Oct 18 11:35:42 dlib2 kernel: CIFS VFS: Error 0xffffffe0 or on cifs_get_inode_info in lookup Oct 18 11:35:42 dlib2 kernel: CIFS VFS: No response buffer Oct 18 11:35:42 dlib2 kernel: CIFS VFS: No response buffer Oct 18 11:35:42 dlib2 kernel: CIFS VFS: Send error in Close = -11 Oct 18 11:36:50 dlib2 kernel: CIFS VFS: No response buffer Stats also shows: 2156 session 1688 share...

/* Cc: samba list */ Vincent Marty wrote: > Hi Ogi ! > Did you find a solution to the problem you described in a post in > linux.samba in dec 2004 ? > I get the same messages from Fedora Core 3 when accessing to a iMax > under Mac Os 10.3. Hi! Since I started to use Debian kernel 2.6.10 (in unstable), the problem disappeared. Fedora Core 3 uses 2.6.10 too so I don't know

...a large number of these (~30-50) CIFS VFS: CIFS: caught signal CIFS VFS: Send error in write = -4 followed by a number of these (~20-25) CIFS VFS: Need to reconnect after session died to server CIFS VFS: Send error in write = -5 and finally (varies) CIFS VFS: Error 0xfffffffb or (-5 decimal) on cifs_get_inode_info in lookup sometimes there is a large block of CIFS VFS: CIFS: caught signal during the session. After that, the system needs to be rebooted. Exporting the same partition via samba on the linux box and initiating the same transfer from the windows system works fine, so I don't think it is...