On 24-Oct-06, at 9:11 PM, James McPherson wrote:

this error from the marvell88sx driver is of concern, The 10b8b decode
and disparity error messages make me think that you have a bad piece
of hardware. I hope it's not your controller but I can't tell without more
data. You should have a look at the iostat -En output for the device
on marvell88sx instance #0, attached as port 3. If there are any error
counts above 0 then - after checking /var/adm/messages for medium
errors - you should probably replace the disk.


I have just tried to do a 'zpool scrub' and I got the same result - a panic right when the scrub finishes (no errors found during / after panic). So I guess this problem is reproducible (and might not be an intermittent hardware malfunction).

It is funny I get the marvell88sx driver error for port 3 as that is the Solaris UFS drive, whereas the rest of the ports are setup for ZFS. Since the scrub seems to be causing the panic, I don't see why an error on the root drive would be the root cause.

Note that this error comes in the log after it is trying to make a dump of the panic: "genunix: [ID 111219 kern.notice] dumping to /dev/ dsk/c0t3d0s1, offset 860356608, content: kernel"


By the way, this is what iostat -En shows for port 3:
c0t3d0           Soft Errors: 24 Hard Errors: 0 Transport Errors: 0
Vendor: ATA      Product: ST3320620AS      Revision: C    Serial No:
Size: 320.07GB <320072932864 bytes>
Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0
Illegal Request: 24 Predictive Failure Analysis: 0


And this is shown on the rest of the ports:
c0t?d0           Soft Errors: 6 Hard Errors: 0 Transport Errors: 0
Vendor: ATA      Product: ST3320620AS      Revision: C    Serial No:
Size: 320.07GB <320072932864 bytes>
Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0
Illegal Request: 6 Predictive Failure Analysis: 0


Thanks,
Siegfried
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss

Reply via email to