On Oct 23, 2009, at 3:19 PM, Eric Schrock wrote:

On 10/23/09 15:05, Cindy Swearingen wrote:
I'm stumped too. Someone with more FM* experience needs to comment.

Looks like your errlog may have been rotated out of existence - see if there is a .X or .gz version in /var/fm/fmd/errlog*. The list.suspect fault should be including a location field that would contain the human readable name for the vdev, but this work (extending the libtopo scheme to support enumeration and label properties) hasn't yet been done. There is also a small change that needs to be made to fmd to support location for non-FRUs. You should to able to do "echo ::spa -c | mdb -k" and look for that vdev id, assuming the vdev is still active on the system.

These are the guids, correct?  If so, then "zdb -C" will show them.
Conversion of hex-decimal or verse vica is an exercise for the reader.
 -richard


- Eric

Cindy
On 10/23/09 14:52, sean walmsley wrote:
Thanks for this information.

We have a weekly scrub schedule, but I ran another just to be sure :-) It completed with 0 errors.

Running fmdump -eV gives:
TIME                           CLASS
fmdump: /var/fm/fmd/errlog is empty

Dumping the faultlog (no -e) does give some output, but again there are no "human readable" identifiers:

... (some stuff omitted)
       (start fault-list[0])
       nvlist version: 0
               version = 0x0
               class = fault.fs.zfs.device
               certainty = 0x64
               asru = (embedded nvlist)
               nvlist version: 0
                       version = 0x0
                       scheme = zfs
                       pool = 0x4fcdc2c9d60a5810
                       vdev = 0x179e471c0732582
               (end asru)

               resource = (embedded nvlist)
               nvlist version: 0
                       version = 0x0
                       scheme = zfs
                       pool = 0x4fcdc2c9d60a5810
                       vdev = 0x179e471c0732582
               (end resource)

       (end fault-list[0])

So, I'm still stumped.
_______________________________________________
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

_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss

Reply via email to