Actions
Bug #4983
closed
need to collect metaslab information via mdb
Start date:
2014-07-09
Due date:
% Done:
100%
Estimated time:
Difficulty:
Medium
Tags:
needs-triage
Gerrit CR:
External Bug:
Description
George Wilson:
Today we use 'zdb' to gather much of the information about ZFS pools. The problem is that when the pool is very full or fragmented the 'zdb' command will fail. We need an easy way to gather information about the free space and it's makeup via mdb that support could collect.
Updated by Electric Monk over 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