On Mon, Jul 19, 2010 at 4:26 PM, Richard Elling <rich...@nexenta.com> wrote:

> Aren't you assuming the I/O error comes from the drive?
> fmdump -eV

okay - I guess I am. Is this just telling me "hey stupid, a checksum
failed" ? In which case why did this never resolve itself and the
specific device get marked as degraded?

Apr 04 2010 21:52:38.920978339 ereport.fs.zfs.checksum
nvlist version: 0
        class = ereport.fs.zfs.checksum
        ena = 0x64350d4040300c01
        detector = (embedded nvlist)
        nvlist version: 0
                version = 0x0
                scheme = zfs
                pool = 0xfd80ebd352cc9271
                vdev = 0x29282dc6fa073a2
        (end detector)

        pool = tank
        pool_guid = 0xfd80ebd352cc9271
        pool_context = 0
        pool_failmode = wait
        vdev_guid = 0x29282dc6fa073a2
        vdev_type = disk
        vdev_path = /dev/dsk/c2t5d0s0
        vdev_devid = id1,s...@sata_____st31500341as________________9vs077gt/a
        parent_guid = 0xc2d5959dd2c07bf7
        parent_type = raidz
        zio_err = 0
        zio_offset = 0x40abbf2600
        zio_size = 0x200
        zio_objset = 0x10
        zio_object = 0x1c06000
        zio_level = 2
        zio_blkid = 0x0
        __ttl = 0x1
        __tod = 0x4bb96c96 0x36e503a3
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss

Reply via email to