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@opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/zfs-discuss -- Eric Schrock, Fishworks http://blogs.sun.com/eschrock
_______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
