Project

General

Profile

Bug #6736

ZFS per-vdev ZAPs

Added by Matthew Ahrens about 4 years ago. Updated about 4 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Matthew Ahrens
Category:
zfs - Zettabyte File System
Start date:
2016-03-10
Due date:
% Done:

100%

Estimated time:
Difficulty:
Medium
Tags:
needs-triage
Gerrit CR:

Description

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.

History

#1

Updated by Electric Monk about 4 years ago

  • % Done changed from 0 to 100
  • Status changed from New to Closed

git commit 215198a6ad15cf4832370e2f19247abeb36b951a

commit  215198a6ad15cf4832370e2f19247abeb36b951a
Author: Joe Stein <joe.stein@delphix.com>
Date:   2016-04-14T16:19:36.000Z

    6736 ZFS per-vdev ZAPs
    Reviewed by: Matthew Ahrens <mahrens@delphix.com>
    Reviewed by: John Kennedy <john.kennedy@delphix.com>
    Reviewed by: George Wilson <george.wilson@delphix.com>
    Reviewed by: Don Brady <don.brady@intel.com>
    Reviewed by: Dan McDonald <danmcd@omniti.com>
    Approved by: Richard Lowe <richlowe@richlowe.net>

Also available in: Atom PDF