Bug 827095

Summary:	CIFS issue
Product:	Red Hat Enterprise Linux 5	Reporter:	Audric DUCHET <aduchet-prest>
Component:	kernel	Assignee:	Sachin Prabhu <sprabhu>
Status:	CLOSED NOTABUG	QA Contact:	Red Hat Kernel QE team <kernel-qe>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	5.8	CC:	cifs-maint, gdeschner, jlayton, prc, rwheeler, sbose
Target Milestone:	rc
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-04-30 10:03:39 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Audric DUCHET 2012-05-31 15:17:16 UTC

Hello,

We have cifs issue on a redhat Red Hat Enterprise Linux Server release 5.8. 

Have you an idea on this issue ? 


/VAR/LOG/messages results


May 31 08:08:57 pub1ppl kernel:  CIFS VFS: No response for cmd 50 mid 64003
May 31 08:09:03 pub1ppl kernel:  CIFS VFS: Bad protocol string signature header 4
May 31 08:09:03 pub1ppl kernel:  CIFS VFS: bad smb detected. The Mid=64007
May 31 08:09:18 pub1ppl kernel:  CIFS VFS: No response for cmd 50 mid 64007
May 31 08:09:21 pub1ppl kernel:  CIFS VFS: Bad protocol string signature header 4
May 31 08:09:21 pub1ppl kernel:  CIFS VFS: bad smb detected. The Mid=64013
May 31 08:09:36 pub1ppl kernel:  CIFS VFS: No response for cmd 50 mid 64013
May 31 08:09:42 pub1ppl kernel:  CIFS VFS: Bad protocol string signature header 4
May 31 08:09:42 pub1ppl kernel:  CIFS VFS: bad smb detected. The Mid=64017
May 31 08:09:57 pub1ppl kernel:  CIFS VFS: No response for cmd 50 mid 64017



dmesg results

 CIFS VFS: No response for cmd 50 mid 64003
 CIFS VFS: Bad protocol string signature header 4
 CIFS VFS: bad smb detected. The Mid=64007
Bad SMB: : dump of 48 bytes of data at 0xffff8106233f90c0
 00000040 00000004 00000032 80018800 @ . . . . . . . 2 . . . . . . .
 00000000 00000000 00000000 31340040 . . . . . . . . . . . . @ . 4 1
 fa070800 0400020a 02000000 00003800 . . . ú . . . . . . . . . 8 . .
 CIFS VFS: No response for cmd 50 mid 64007
 CIFS VFS: Bad protocol string signature header 4
 CIFS VFS: bad smb detected. The Mid=64013
Bad SMB: : dump of 48 bytes of data at 0xffff8106233f90c0
 00000040 00000004 00000032 80018800 @ . . . . . . . 2 . . . . . . .
 00000000 00000000 00000000 31340040 . . . . . . . . . . . . @ . 4 1
 fa0d0800 0400020a 02000000 00003800 . . . ú . . . . . . . . . 8 . .
 CIFS VFS: No response for cmd 50 mid 64013
 CIFS VFS: Bad protocol string signature header 4
 CIFS VFS: bad smb detected. The Mid=64017
Bad SMB: : dump of 48 bytes of data at 0xffff8106233f9440
 00000040 00000004 00000032 80018800 @ . . . . . . . 2 . . . . . . .
 00000000 00000000 00000000 31340040 . . . . . . . . . . . . @ . 4 1
 fa110800 0400020a 02000000 00003800 . . . ú . . . . . . . . . 8 . .
 CIFS VFS: No response for cmd 50 mid 64017

Comment 1 Jeff Layton 2012-05-31 18:44:46 UTC

At first glance, looks like some kind of alignment problem or the server is sending malformed replies.

Comment 2 Sachin Prabhu 2012-05-31 20:44:21 UTC

How often does this happen?
Is it persistent or transient?
Do you have a tcpdump taken at the time this was happening? Please use the -s0 option to capture the dumps.
What server? 
And what were the mount options?

Sachin Prabhu

Comment 3 Sachin Prabhu 2012-05-31 20:46:09 UTC

It would be preferable in this case to go through the support channels. Can you please open a support issue with support.

Comment 4 Sachin Prabhu 2013-04-30 10:03:39 UTC

Closing this issue because of a lack of updates.