Bug #5211
'fmadm repaired <record>' do not work with fault.fs.zfs.pool
Status:
New
Priority:
Normal
Assignee:
-
Category:
-
Start date:
2014-10-05
Due date:
% Done:
0%
Estimated time:
Difficulty:
Medium
Tags:
needs-triage
Gerrit CR:
Description
root@srv249:~# fmadm faulty
--------------- ------------------------------------ -------------- ---------
TIME EVENT-ID MSG-ID SEVERITY
--------------- ------------------------------------ -------------- ---------
Oct 04 21:13:58 5221658b-6128-c988-f678-a169dad8e4e9 ZFS-8000-CS Major
Host : srv249
Platform : System-Product-Name Chassis_id : System-Serial-Number
Product_sn :
Fault class : fault.fs.zfs.pool
Affects : zfs://pool=ssd01
faulted but still in service
Problem in : zfs://pool=ssd01
faulted but still in service
Description : A ZFS pool failed to open. Refer to
http://illumos.org/msg/ZFS-8000-CS for more information.
Response : No automated response will occur.
Impact : The pool data is unavailable
Action : Run 'zpool status -x' and attach any missing devices, follow
any provided recovery instructions or restore from backup.
root@srv249:~# fmadm repaired zfs://pool=ssd01
fmadm: failed to record repair to zfs://pool=ssd01: specified resource is not known to be faulty
History
Updated by Franz Skale about 5 years ago
Updated by Igor Kozhukhov wrote:
[...]
Hi,
i can reproduce the problem using joyent_20150403T090417Z.
Fault class : fault.fs.zfs.device
Affects : zfs://pool=pool01/vdev=98aca9050596c70a
faulted but still in service
Problem in : zfs://pool=pool01/vdev=98aca9050596c70a
faulted but still in service
fmadm repair pool=pool01/vdev=98aca9050596c70a
fmadm: failed to record repair to pool=pool01/vdev=98aca9050596c70a: specified resource is not known to be faulty
Bugfix available soon ?
Rgds.
Franz