Project

General

Profile

Actions
Copy link

Bug #4982

closed

space_map object should proactively upgrade when feature is enabled

Added by Christopher Siden about 9 years ago. Updated about 9 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Christopher Siden
Category:
zfs - Zettabyte File System
Start date:
2014-07-09
Due date:
% Done:

100%

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

Description

George Wilson:

When you enable the space_map_histogram feature the space_map object will
upgrade the next time it condenses. We should proactively upgrade space_maps
even if they don't need it so that we can start collecting histogram
information more quickly.

Actions
Copy link
 #1

Updated by Electric Monk about 9 years ago

  • Status changed from New to Closed

git commit 2e4c998613148111f2fc5371085331ffb39122ff

commit  2e4c998613148111f2fc5371085331ffb39122ff
Author: George Wilson <george.wilson@delphix.com>
Date:   2014-07-19T20:19:25.000Z

    4976 zfs should only avoid writing to a failing non-redundant top-level vdev
    4977 mdb error in ::spa_space from space_cb() if a metaslab's ms_sm is NULL
    4978 ztest fails in get_metaslab_refcount()
    4979 extend free space histogram to device and pool
    4980 metaslabs should have a fragmentation metric
    4981 remove fragmented ops vector from block allocator
    4982 space_map object should proactively upgrade when feature is enabled
    4983 need to collect metaslab information via mdb
    4984 device selection should use fragmentation metric
    Reviewed by: Matthew Ahrens <mahrens@delphix.com>
    Reviewed by: Adam Leventhal <adam.leventhal@delphix.com>
    Reviewed by: Christopher Siden <christopher.siden@delphix.com>
    Approved by: Garrett D'Amore <garrett@damore.org>

Actions
Copy link

Also available in: Atom PDF