Hi all,
ZFS send a message to FMA in case of disk failure.
The detail of the message reference a vdev by an hexadecimal number as:
# *fmdump -V -u 50ea07a0-2cd9-6bfb-ff9e-e219740052d5*
TIME UUID SUNW-MSG-ID
Feb 18 11:07:29.5195 50ea07a0-2cd9-6bfb-ff9e-e219740052d5 ZFS-8000-D3
TIME CLASS ENA
Feb 18 11:07:27.8476 ereport.fs.zfs.vdev.open_failed 0xb22406c635500401
nvlist version: 0
version = 0x0
...
nvlist version: 0
version = 0x0
scheme = zfs
pool = 0x3a2ca6bebd96cfe3
_*vdev = 0xedef914b5d9eae8d*_
I have search how to join the vdev number
0xedef914b5d9eae8d to a failed device, but I found
no way to make the link.
Can someone help ?
Thank you.
Alain Ch?reau.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://mail.opensolaris.org/pipermail/zfs-discuss/attachments/20080904/ac0baadb/attachment.html>
You should be able to do ''zpool status -x'' to find out what vdev is broken. A useful extension to the DE would be to add a label to the suspect corresponding to <pool>/<vdev>. - Eric On Thu, Sep 04, 2008 at 06:34:33PM +0200, Alain Ch?reau wrote:> Hi all, > > ZFS send a message to FMA in case of disk failure. > The detail of the message reference a vdev by an hexadecimal number as: > > # *fmdump -V -u 50ea07a0-2cd9-6bfb-ff9e-e219740052d5* > TIME UUID SUNW-MSG-ID > Feb 18 11:07:29.5195 50ea07a0-2cd9-6bfb-ff9e-e219740052d5 ZFS-8000-D3 > > TIME CLASS ENA > Feb 18 11:07:27.8476 ereport.fs.zfs.vdev.open_failed > 0xb22406c635500401 > > nvlist version: 0 > version = 0x0 > ... > nvlist version: 0 > version = 0x0 > scheme = zfs > pool = 0x3a2ca6bebd96cfe3 > _*vdev = 0xedef914b5d9eae8d*_ > > > I have search how to join the vdev number > 0xedef914b5d9eae8d to a failed device, but I found > no way to make the link. > > Can someone help ? > > Thank you. > > Alain Ch?reau. > > >> _______________________________________________ > zfs-discuss mailing list > zfs-discuss at opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/zfs-discuss-- Eric Schrock, Fishworks http://blogs.sun.com/eschrock
Cindy.Swearingen at Sun.COM
2008-Sep-04 17:10 UTC
[zfs-discuss] Explaining ZFS message in FMA
Alain,
I think you want to use fmdump -eV to display the extended device
information. See the output below.
Cindy
class = ereport.fs.zfs.checksum
ena = 0x3242b9cdeac00401
detector = (embedded nvlist)
nvlist version: 0
version = 0x0
scheme = zfs
pool = 0x5fd04b3a3f98df8e
vdev = 0x6ae5803769caa878
(end detector)
pool = sunray
pool_guid = 0x5fd04b3a3f98df8e
pool_context = 0
vdev_guid = 0x6ae5803769caa878
vdev_type = disk
vdev_path = /dev/dsk/c1t1d0s7
vdev_devid = id1,sd at SSEAGATE_ST373307LSUN72G_3HZ9N5X700007520M2TB/h
Alain Ch?reau wrote:> Hi all,
>
> ZFS send a message to FMA in case of disk failure.
> The detail of the message reference a vdev by an hexadecimal number as:
>
> # *fmdump -V -u 50ea07a0-2cd9-6bfb-ff9e-e219740052d5*
> TIME UUID SUNW-MSG-ID
> Feb 18 11:07:29.5195 50ea07a0-2cd9-6bfb-ff9e-e219740052d5 ZFS-8000-D3
>
> TIME CLASS ENA
> Feb 18 11:07:27.8476 ereport.fs.zfs.vdev.open_failed
0xb22406c635500401
>
> nvlist version: 0
> version = 0x0
> ...
> nvlist version: 0
> version = 0x0
> scheme = zfs
> pool = 0x3a2ca6bebd96cfe3
> _*vdev = 0xedef914b5d9eae8d*_
>
>
> I have search how to join the vdev number
> 0xedef914b5d9eae8d to a failed device, but I found
> no way to make the link.
>
> Can someone help ?
>
> Thank you.
>
> Alain Ch?reau.
>
>
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> zfs-discuss mailing list
> zfs-discuss at opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/zfs-discuss