Siegfried,
Can you provide the panic string that you are seeing? We should be able
to pull out the persistent error log information from the corefile. You
can take a look at spa_get_errlog() function as a starting point.
Additionally, you can look at the corefile using mdb and take a look at
the vdev error stats. Here's an example (hopefully the formatting
doesn't get messed up):
> ::spa -v
ADDR STATE NAME
0000060004473680 ACTIVE test
ADDR STATE AUX DESCRIPTION
0000060004bcb500 HEALTHY - root
0000060004bcafc0 HEALTHY - /dev/dsk/c0t2d0s0
> 0000060004bcb500::vdev -re
ADDR STATE AUX DESCRIPTION
0000060004bcb500 HEALTHY - root
READ WRITE FREE CLAIM IOCTL
OPS 0 0 0 0 0
BYTES 0 0 0 0 0
EREAD 0
EWRITE 0
ECKSUM 0
0000060004bcafc0 HEALTHY - /dev/dsk/c0t2d0s0
READ WRITE FREE CLAIM IOCTL
OPS 0x17 0x1d2 0 0 0
BYTES 0x19c000 0x11da00 0 0 0
EREAD 0
EWRITE 0
ECKSUM 0
This will show you and read/write/cksum errors.
Thanks,
George
Siegfried Nikolaivich wrote:
Hello All,
I am wondering if there is a way to save the scrub results right before the
scrub is complete.
After upgrading to Solaris 10U3 I still have ZFS panicing right as the scrub completes.
The scrub results seem to be "cleared" when system boots back up, so I never
get a chance to see them.
Does anyone know of a simple way?
This message posted from opensolaris.org
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
