Hi,
I just switched my 8.1-R/amd64 (dual Opteron) system from ATA over to the
new mvs driver, and started seeing a whole bunch of errors (which appear to
have hosed one of my zfs volumes during a scrub) - anyone know what the
following errors actually mean?
The machine has 2 * 88SX6081's in it:
"
Sep 28 19:58:49 kernel: mvs0: <Marvell 88SX6081 SATA controller> port
0x3000-0x30ff mem 0xd0100000-0xd01fffff,0xd0400000-0xd07fffff irq 24 at
device 4.0 on pci17
Sep 28 19:58:49 kernel: mvs0: Gen-II, 8 3Gbps ports, Port Multiplier
...
Sep 28 19:58:49 kernel: mvs1: <Marvell 88SX6081 SATA controller> port
0x4000-0x40ff mem 0xd0c00000-0xd0cfffff,0xd0800000-0xd0bfffff irq 28 at
device 4.0 on pci18
Sep 28 19:58:49 kernel: mvs1: Gen-II, 8 3Gbps ports, Port Multiplier
supported
"
Under 7.2 they ran fine, with the ATA driver. I use ZFS on this machine -
and both pools were scrubbed before the upgrade (and backed up
fortunately!).
With the mvs driver, during a scrub of the main volume, I see:
"
Sep 29 08:56:13 kernel: mvsch12: EMPTY CRPB 6 (->14) 1 4000
Sep 29 08:56:13 kernel: mvsch12: EMPTY CRPB 7 (->14) 0 4000
Sep 29 08:56:13 kernel: mvsch12: EMPTY CRPB 8 (->14) 2 4000
"
[repeated a lot - interspersed with zfs reporting problems with files, on
all the devices in the pool]
I then also get a whole bunch of:
"
Sep 29 08:56:56 kernel: mvsch0: Timeout on slot 1
Sep 29 08:56:56 kernel: mvsch0: iec 02000000 sstat 00000123 serr 00000000
edma_s 00001020 dma_c 00000000 dma_s 00000000 rs 00000006 statu
s 40
Sep 29 08:56:56 kernel: mvsch0: ... waiting for slots 00000004
Sep 29 08:56:56 kernel: mvsch12: Timeout on slot 5
Sep 29 08:56:56 kernel: mvsch12: iec 02000000 sstat 00000123 serr 00000000
edma_s 00001121 dma_c 00000000 dma_s 00000000 rs 00000028 stat
us 40
"
The system has 2 pools (one is 12 disks of mirrored pairs - each side of
the mirror is on alternate Marvell's), the other is 1 RAIDZ of 4 disks, 2
are on alternate Marvell's - the other 2 drives are on the motherboards
nForce CK804 ports).
I scrubbed the second pool yesterday without incident, so this only seemed
to happen using drives exclusively on the 88SX6081's (or the I/O system is
stressed, running the I/O for all 12 drives through the Marvells, as
opposed to just the I/O for 2 drives [1 each] through the Marvells when
the other pool is scrubbed).
-Karl
_______________________________________________
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
