Errors on MPT (LSI3801E)
d_elbracht
d_elbracht at ecngs.de
Mon Apr 21 13:21:30 UTC 2008
We are seeing occasional errors like below
System is a TYAN S3992, dual am64, 32GB RAM, cvsupd 7.0-STABLE FreeBSD
7.0-STABLE #4: Mon Mar 31 15:06:55 CEST 2008
An Infortrend S16S-G1030 + S16S-J1000-S is connected to an LSI3801-E.
A Media-Scan on the Infortrend does NOT show any errors. The 3801 was
swapped, still errors.
besides the LSI 3801-E, there are 4 other controllers used with NO errors at
all:
twa0: <3ware 9000 series Storage Controller> port 0x5c00-0x5c3f mem
0xcc000000-0xcdffffff,0xfddff000-0xfddfffff irq 20 at device 5.0 on pci2
twa0: [ITHREAD]
twa0: INFO: (0x15: 0x1300): Controller details:: Model 9550SX-12, 12 ports,
Firmware FE9X 3.08.02.007, BIOS BE9X 3.08.00.002
atapci0: <ServerWorks HT1000 SATA150 controller> port
0x7c00-0x7c07,0x7880-0x7883,0x7800-0x7807,0x7480-0x7483,0x7400-0x741f mem
0xfdefe000-0xfdefffff irq 11 at device 14.0 on pci1
atapci0: [ITHREAD]
ata2: <ATA channel 0> on atapci0
ata2: [ITHREAD]
ata3: <ATA channel 1> on atapci0
ata3: [ITHREAD]
ata4: <ATA channel 2> on atapci0
ata4: [ITHREAD]
ata5: <ATA channel 3> on atapci0
ata5: [ITHREAD]
atapci1: <ServerWorks HT1000 UDMA100 controller> port
0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xffa0-0xffaf at device 2.1 on pci0
ata0: <ATA channel 0> on atapci1
ata0: [ITHREAD]
ata1: <ATA channel 1> on atapci1
ata1: [ITHREAD]
isp0: <Qlogic ISP 2312 PCI FC-AL Adapter> port 0x8800-0x88ff mem
0xfdfff000-0xfdffffff irq 22 at device 4.0 on pci3
isp0: [ITHREAD]
isp0: Board Type 2312, Chip Revision 0x2, loaded F/W Revision 3.3.19
aac0: <ICP RAID ICP5805BL> mem 0xfe400000-0xfe5fffff irq 28 at device 14.0
on pci7
aac0: Enabling 64-bit address support
aac0: New comm. interface enabled
aac0: [ITHREAD]
aac0: ICP ICP5805BL, aac driver 2.0.0-1
aac0: Error 5 sending VMIoctl command
mpt0: <LSILogic SAS/SATA Adapter> port 0xb000-0xb0ff mem
0xfeafc000-0xfeafffff,0xfeae0000-0xfeaeffff irq 30 at device 0.0 on pci9
mpt0: [ITHREAD]
mpt0: MPI Version=1.5.17.0
mpt0: mpt_cam_event: 0x16
mpt0: mpt_cam_event: 0x16
Apr 21 13:01:21 spool1 kernel: bad block -289758967411216238, ino 3498114
Apr 21 13:01:21 spool1 kernel: pid 49 (softdepflush), uid 0 inumber 3498114
on /news2/spool/news/28: bad block
Apr 21 13:01:21 spool1 kernel: bad block -1974150432459695593, ino 3498114
Apr 21 13:01:21 spool1 kernel: pid 49 (softdepflush), uid 0 inumber 3498114
on /news2/spool/news/28: bad block
Apr 21 13:01:21 spool1 kernel: bad block 3924693657070553602, ino 3498114
Apr 21 13:01:21 spool1 kernel: pid 49 (softdepflush), uid 0 inumber 3498114
on /news2/spool/news/28: bad block
Apr 21 13:01:21 spool1 kernel: bad block -1880893109408328697, ino 3498114
Apr 21 13:01:21 spool1 kernel: pid 49 (softdepflush), uid 0 inumber 3498114
on /news2/spool/news/28: bad block
Apr 21 13:01:21 spool1 kernel: bad block 7443855300351118928, ino 3498114
Apr 21 13:01:21 spool1 kernel: pid 49 (softdepflush), uid 0 inumber 3498114
on /news2/spool/news/28: bad block
Apr 21 13:01:21 spool1 kernel: bad block 8635841315344043953, ino 3498114
Apr 21 13:01:21 spool1 kernel: pid 49 (softdepflush), uid 0 inumber 3498114
on /news2/spool/news/28: bad block
Apr 21 13:01:21 spool1 kernel: bad block -5554226653918778662, ino 3498114
Apr 21 13:01:21 spool1 kernel: pid 49 (softdepflush), uid 0 inumber 3498114
on /news2/spool/news/28: bad block
Apr 21 13:01:21 spool1 kernel: bad block 3538396528377557312, ino 3498114
Apr 21 13:01:21 spool1 kernel: pid 49 (softdepflush), uid 0 inumber 3498114
on /news2/spool/news/28: bad block
Apr 21 13:01:21 spool1 kernel: bad block 4440353572002830628, ino 3498114
Apr 21 13:01:21 spool1 kernel: pid 49 (softdepflush), uid 0 inumber 3498114
on /news2/spool/news/28: bad block
Apr 21 13:01:21 spool1 kernel:
g_vfs_done():da53[READ(offset=709705054559076352, length=65536)]error = 5
Apr 21 13:01:21 spool1 kernel: bad block 5392362287553715125, ino 3498114
Apr 21 13:01:21 spool1 kernel: pid 49 (softdepflush), uid 0 inumber 3498114
on /news2/spool/news/28: bad block
Apr 21 13:01:21 spool1 kernel: bad block -2588558218317828228, ino 3498114
Apr 21 13:01:21 spool1 kernel: pid 49 (softdepflush), uid 0 inumber 3498114
on /news2/spool/news/28: bad block
Apr 21 13:01:21 spool1 kernel: bad block 4848756102075306261, ino 3498114
Apr 21 13:01:21 spool1 kernel: pid 49 (softdepflush), uid 0 inumber 3498114
on /news2/spool/news/28: bad block
Apr 21 13:01:21 spool1 kernel: bad block -4433087689437922947, ino 3498114
Apr 21 13:01:21 spool1 kernel: pid 49 (softdepflush), uid 0 inumber 3498114
on /news2/spool/news/28: bad block
Apr 21 13:01:21 spool1 kernel: bad block 4450693383788471588, ino 3498114
Apr 21 13:01:21 spool1 kernel: pid 49 (softdepflush), uid 0 inumber 3498114
on /news2/spool/news/28: bad block
Apr 21 13:01:21 spool1 kernel: bad block 3047254019211875932, ino 3498114
Apr 21 13:01:21 spool1 kernel: pid 49 (softdepflush), uid 0 inumber 3498114
on /news2/spool/news/28: bad block
Any clue ?
best regards
Dieter
More information about the freebsd-scsi
mailing list