space_map object should proactively upgrade when feature is enabled
zfs - Zettabyte File System
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.
Updated by Electric Monk about 9 years ago
- Status changed from New to Closed
commit 2e4c998613148111f2fc5371085331ffb39122ff Author: George Wilson <firstname.lastname@example.org> 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 <email@example.com> Reviewed by: Adam Leventhal <firstname.lastname@example.org> Reviewed by: Christopher Siden <email@example.com> Approved by: Garrett D'Amore <firstname.lastname@example.org>