ZFS per-vdev ZAPs
vdevs currently have a packed nvlist for config stored in their on-disk labels. Instead of adding to this every time we want a new config, we can make a new ZAP for every vdev and store its object # instead. It's also confusing that the config is stored both in the label and in the MOS, and some fields of the config are only valid in the MOS (the version in the label could be out of date). These fields should be stored in the new per-vdev ZAP objects.
Updated by Electric Monk over 5 years ago
- Status changed from New to Closed
- % Done changed from 0 to 100
commit 215198a6ad15cf4832370e2f19247abeb36b951a Author: Joe Stein <firstname.lastname@example.org> Date: 2016-04-14T16:19:36.000Z 6736 ZFS per-vdev ZAPs Reviewed by: Matthew Ahrens <email@example.com> Reviewed by: John Kennedy <firstname.lastname@example.org> Reviewed by: George Wilson <email@example.com> Reviewed by: Don Brady <firstname.lastname@example.org> Reviewed by: Dan McDonald <email@example.com> Approved by: Richard Lowe <firstname.lastname@example.org>