[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: data overrun detected in Data-in phase



Martin wrote:
On Thu, 2008-01-31 at 18:27 +0100, BERTRAND Joël wrote:
	Hello,

I'm using a Adaptec 29160 in a U60/SMP workstation. For 2.6.23.11, I see these messages in log file :

(scsi2:A:4:0): data overrun detected in Data-in phase.  Tag == 0x12.
(scsi2:A:4:0): Have seen Data Phase.  Length = 24576.  NumSGs = 1.
sg[0] - Addr 0x0c087e840 : Length 32
(scsi2:A:4:0): data overrun detected in Data-in phase.  Tag == 0x42.
(scsi2:A:4:0): Have seen Data Phase.  Length = 8192.  NumSGs = 1.
sg[0] - Addr 0x0c087e820 : Length 32
(scsi2:A:4:0): data overrun detected in Data-in phase.  Tag == 0x13.
(scsi2:A:4:0): Have seen Data Phase.  Length = 8192.  NumSGs = 1.
sg[0] - Addr 0x0c087e800 : Length 32
(scsi2:A:4:0): data overrun detected in Data-in phase.  Tag == 0x41.
(scsi2:A:4:0): Have seen Data Phase.  Length = 24576.  NumSGs = 1.
sg[0] - Addr 0x0c087e100 : Length 32
(scsi2:A:4:0): data overrun detected in Data-in phase.  Tag == 0x7a.
(scsi2:A:4:0): Have seen Data Phase.  Length = 8192.  NumSGs = 1.
sg[0] - Addr 0x0c087e7c0 : Length 32
(scsi2:A:4:0): data overrun detected in Data-in phase.  Tag == 0xb.
(scsi2:A:4:0): Have seen Data Phase.  Length = 8192.  NumSGs = 1.
sg[0] - Addr 0x0c087ede0 : Length 32
(scsi2:A:4:0): data overrun detected in Data-in phase.  Tag == 0x54.
(scsi2:A:4:0): Have seen Data Phase.  Length = 8192.  NumSGs = 1.
sg[0] - Addr 0x0c087e180 : Length 32
(scsi2:A:4:0): data overrun detected in Data-in phase.  Tag == 0x30.
(scsi2:A:4:0): Have seen Data Phase.  Length = 8192.  NumSGs = 1.
sg[0] - Addr 0x0c087e160 : Length 32

I don't understand this message. Disk seems to be good. This device is a part of a 7-disk raid6 array. I don't find any information about this message. Any idea ?
It's probably not much help but problems with cabling and termination,
particularly on buses with lots of disks can create lots of seemingly
obscure errors.  Another option would be to temporarily remove the disk
with ID 4; which should tell you if it's a disk specific problem.

	Thanks for your answer. I shall test.

	JKB


Reply to: