zhihui Chen
2009-06-24 03:25:57 UTC
Hello All,
We have a mirrored pool with two Intel X25-E SSDs, recently it
reports read error every several days, "fmdump -eV" outputs like following.
These errors just happens on one fixed disk(c0t0d0s0) and zio_error type is
5 (EIO), fmdump does not report any hardware-related error, such as
ereport.scsi.disk.*, but we are still not sure whether it is a hardware
issue or software issue? Another question, is there any good method to know
what file is accessed when this read error happens?
Jun 16 2009 15:53:25.133358691 ereport.fs.zfs.io
nvlist version: 0
class = ereport.fs.zfs.io
ena = 0xbc53f1f2c8300801
detector = (embedded nvlist)
nvlist version: 0
version = 0x0
scheme = zfs
pool = 0x5642f320bae8cb74
vdev = 0xb5907c14ddc2d15f
(end detector)
pool = rpool
pool_guid = 0x5642f320bae8cb74
pool_context = 0
pool_failmode = continue
vdev_guid = 0xb5907c14ddc2d15f
vdev_type = disk
vdev_path = /dev/dsk/c0t0d0s0
vdev_devid = id1,***@n50015179587a6745/a
parent_guid = 0x50202a355d6ce69e
parent_type = mirror
zio_err = 5
zio_offset = 0xa8de0000
zio_size = 0x20000
zio_objset = 0x2c
zio_object = 0x2e2d2
zio_level = 0
zio_blkid = 0x1b
__ttl = 0x1
__tod = 0x4a374f75 0x7f2e463
Jun 18 2009 18:32:35.931540260 ereport.fs.zfs.io
nvlist version: 0
class = ereport.fs.zfs.io
ena = 0x19e509b9ff800801
detector = (embedded nvlist)
nvlist version: 0
version = 0x0
scheme = zfs
pool = 0x5642f320bae8cb74
vdev = 0xb5907c14ddc2d15f
(end detector)
pool = rpool
pool_guid = 0x5642f320bae8cb74
pool_context = 0
pool_failmode = continue
vdev_guid = 0xb5907c14ddc2d15f
vdev_type = disk
vdev_path = /dev/dsk/c0t0d0s0
vdev_devid = id1,***@n50015179587a6745/a
parent_guid = 0x50202a355d6ce69e
parent_type = mirror
zio_err = 5
zio_offset = 0xa94e0000
zio_size = 0x20000
zio_objset = 0x32
zio_object = 0x862c
zio_level = 0
zio_blkid = 0x4
__ttl = 0x1
__tod = 0x4a3a17c3 0x37862d24
Jun 23 2009 03:10:10.103782168 ereport.fs.zfs.io
nvlist version: 0
class = ereport.fs.zfs.io
ena = 0x82f657f0d9100801
detector = (embedded nvlist)
nvlist version: 0
version = 0x0
scheme = zfs
pool = 0x5642f320bae8cb74
vdev = 0xb5907c14ddc2d15f
(end detector)
pool = rpool
pool_guid = 0x5642f320bae8cb74
pool_context = 0
pool_failmode = continue
vdev_guid = 0xb5907c14ddc2d15f
vdev_type = disk
vdev_path = /dev/dsk/c0t0d0s0
vdev_devid = id1,***@n50015179587a6745/a
parent_guid = 0x50202a355d6ce69e
parent_type = mirror
zio_err = 5
zio_offset = 0xa6080000
zio_size = 0x20000
zio_objset = 0x32
zio_object = 0x726a
zio_level = 0
zio_blkid = 0x0
__ttl = 0x1
__tod = 0x4a3fd712 0x62f9718
Thanks
Zhihui
We have a mirrored pool with two Intel X25-E SSDs, recently it
reports read error every several days, "fmdump -eV" outputs like following.
These errors just happens on one fixed disk(c0t0d0s0) and zio_error type is
5 (EIO), fmdump does not report any hardware-related error, such as
ereport.scsi.disk.*, but we are still not sure whether it is a hardware
issue or software issue? Another question, is there any good method to know
what file is accessed when this read error happens?
Jun 16 2009 15:53:25.133358691 ereport.fs.zfs.io
nvlist version: 0
class = ereport.fs.zfs.io
ena = 0xbc53f1f2c8300801
detector = (embedded nvlist)
nvlist version: 0
version = 0x0
scheme = zfs
pool = 0x5642f320bae8cb74
vdev = 0xb5907c14ddc2d15f
(end detector)
pool = rpool
pool_guid = 0x5642f320bae8cb74
pool_context = 0
pool_failmode = continue
vdev_guid = 0xb5907c14ddc2d15f
vdev_type = disk
vdev_path = /dev/dsk/c0t0d0s0
vdev_devid = id1,***@n50015179587a6745/a
parent_guid = 0x50202a355d6ce69e
parent_type = mirror
zio_err = 5
zio_offset = 0xa8de0000
zio_size = 0x20000
zio_objset = 0x2c
zio_object = 0x2e2d2
zio_level = 0
zio_blkid = 0x1b
__ttl = 0x1
__tod = 0x4a374f75 0x7f2e463
Jun 18 2009 18:32:35.931540260 ereport.fs.zfs.io
nvlist version: 0
class = ereport.fs.zfs.io
ena = 0x19e509b9ff800801
detector = (embedded nvlist)
nvlist version: 0
version = 0x0
scheme = zfs
pool = 0x5642f320bae8cb74
vdev = 0xb5907c14ddc2d15f
(end detector)
pool = rpool
pool_guid = 0x5642f320bae8cb74
pool_context = 0
pool_failmode = continue
vdev_guid = 0xb5907c14ddc2d15f
vdev_type = disk
vdev_path = /dev/dsk/c0t0d0s0
vdev_devid = id1,***@n50015179587a6745/a
parent_guid = 0x50202a355d6ce69e
parent_type = mirror
zio_err = 5
zio_offset = 0xa94e0000
zio_size = 0x20000
zio_objset = 0x32
zio_object = 0x862c
zio_level = 0
zio_blkid = 0x4
__ttl = 0x1
__tod = 0x4a3a17c3 0x37862d24
Jun 23 2009 03:10:10.103782168 ereport.fs.zfs.io
nvlist version: 0
class = ereport.fs.zfs.io
ena = 0x82f657f0d9100801
detector = (embedded nvlist)
nvlist version: 0
version = 0x0
scheme = zfs
pool = 0x5642f320bae8cb74
vdev = 0xb5907c14ddc2d15f
(end detector)
pool = rpool
pool_guid = 0x5642f320bae8cb74
pool_context = 0
pool_failmode = continue
vdev_guid = 0xb5907c14ddc2d15f
vdev_type = disk
vdev_path = /dev/dsk/c0t0d0s0
vdev_devid = id1,***@n50015179587a6745/a
parent_guid = 0x50202a355d6ce69e
parent_type = mirror
zio_err = 5
zio_offset = 0xa6080000
zio_size = 0x20000
zio_objset = 0x32
zio_object = 0x726a
zio_level = 0
zio_blkid = 0x0
__ttl = 0x1
__tod = 0x4a3fd712 0x62f9718
Thanks
Zhihui