Implement autoreplace matching on FRU slot number, i.e. if enclosure and slot number of added device match those of failed (removed) device, do replace automatically (if autoreplace property is set).
The main victim here is syseventd's zfs_mod: - remove lofi autoreplace support - it was intended to simplify testing, but in reality only serves to obscure the code - iterate over spare and l2cache devices as well, allowing setting FRU on them - implement logic for FRU based autoreplace as path/physpath will be different there You can view, comment on, or merge this pull request online at: https://github.com/openzfs/openzfs/pull/416 -- Commit Summary -- * 7823 implement autoreplace matching based on FRU slot number -- File Changes -- M usr/src/cmd/syseventd/modules/zfs_mod/Makefile (4) M usr/src/cmd/syseventd/modules/zfs_mod/zfs_mod.c (600) M usr/src/lib/libzfs/common/libzfs.h (4) M usr/src/lib/libzfs/common/libzfs_fru.c (82) M usr/src/lib/libzfs/common/libzfs_pool.c (5) M usr/src/lib/libzfs/common/mapfile-vers (3) M usr/src/uts/common/fs/zfs/vdev.c (7) M usr/src/uts/common/fs/zfs/vdev_disk.c (13) M usr/src/uts/common/fs/zfs/zfs_ioctl.c (5) -- Patch Links -- https://github.com/openzfs/openzfs/pull/416.patch https://github.com/openzfs/openzfs/pull/416.diff -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/openzfs/openzfs/pull/416 ------------------------------------------ openzfs-developer Archives: https://openzfs.topicbox.com/groups/developer/discussions/T97ec8ed8719a97d0-M061f57397af39cc223d2bb20 Powered by Topicbox: https://topicbox.com
