On Apr 5, 2010, at 11:43 AM, Garrett D'Amore wrote: > > I see ereport.fs.zfs.io_failure, and ereport.fs.zfs.probe_failure. Also, > ereport.io.service.lost and ereport.io.device.inval_state. There is indeed a > fault.fs.zfs.device in the list as well.
The ereports are not interesting, only the fault. In FMA, ereports contribute to diagnosis, but faults are the only thing that are presented to the user and retire agents. > Everything seems to be correct *except* that ZFS isn't automatically doing > the replace operation with the hot spare. > > It feels to me like this is possibly a ZFS bug --- perhaps ZFS is expecting a > specific set of FMA faults that only sd delivers? (Recall this is with a > different target device.) Yes, it may be a bug. You will have to step through the zfs retire agent to see what goes wrong when it receives the list.suspect event. This code path is tested many, many times every day, so it's not as obvious as "this doesn't work." The ZFS retire agent subscribes only to ZFS faults. The underlying driver or other telemetry has no bearing on the diagnosis or associated action. - Eric _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
