Are you running the latest bits? The reason I ask is that we introduced
the spacemap_histogram as a feature but did not expose it via the cli
until later.
Here's all the related commits from newest to oldest:
commit 7a09f97bc0d52b763c580864e78a665b15be37f8
Author: George Wilson <***@delphix.com>
Date: Tue Sep 16 11:51:18 2014 -0800
5147 zpool list -v should show individual disk capacity
Reviewed by: Adam Leventhal <***@delphix.com>
Reviewed by: Christopher Siden <***@delphix.com>
Reviewed by: Matthew Ahrens <***@delphix.com>
Reviewed by: Richard Elling <***@gmail.com>
Approved by: Dan McDonald <***@omniti.com>
commit 2e4c998613148111f2fc5371085331ffb39122ff
Author: George Wilson <***@delphix.com>
Date: Sat Jul 19 12:19:24 2014 -0800
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 <***@delphix.com>
Reviewed by: Adam Leventhal <***@delphix.com>
Reviewed by: Christopher Siden <***@delphix.com>
Approved by: Garrett D'Amore <***@damore.org>
commit 0713e232b7712cd27d99e1e935ebb8d5de61c57d
Author: George Wilson <***@delphix.com>
Date: Tue Oct 1 13:25:53 2013 -0800
4101 metaslab_debug should allow for fine-grained control
4102 space_maps should store more information about themselves
4103 space map object blocksize should be increased
4104 ::spa_space no longer works
4105 removing a mirrored log device results in a leaked object
4106 asynchronously load metaslab
Reviewed by: Matthew Ahrens <***@delphix.com>
Reviewed by: Adam Leventhal <***@delphix.com>
Reviewed by: Sebastien Roy <***@delphix.com>
Approved by: Garrett D'Amore <***@damore.org>
Thanks,
George
Post by Vadim Comanescu via illumos-zfsSorry, wanted to say zpool list from the beginning, just mistyped.
When creating a new pool the FRAG column would indeed be available,
for existing pools that have the spacemap_histogram feature active is
NAME SIZE ALLOC FREE EXPANDSZ CAP DEDUP HEALTH ALTROOT
tank 10.9T 2.56T 8.31T - 23% 1.00x ONLINE -
NAME PROPERTY VALUE SOURCE
My question was actually related to this case when the feature is
active and the frag column is missing. Thanks.
Hi,
Have you tried spool list?
Granted my distro is FreeBSD but /zfs list/ does yield slightly
diff info than /zpool list/.
So try z/pool list/.
- aurf
"Janitorial Services"
On Sep 12, 2014, at 11:22 AM, Vadim Comanescu via illumos-zfs
Post by Vadim Comanescu via illumos-zfsHi George,
Thank you for the explanations. Really useful. Looking over the
current illumos-gate master I don't see the FRAG column available
on the the output of zfs list. Is that something that is present
only at Delphix at the moment?
Regards.
On Wed, Sep 10, 2014 at 6:27 PM, George Wilson via illumos-zfs
You can use it on existing pools but the histogram only gets
created when you condense a space_map (a process by which ZFS
tries to make the space_map ondisk smaller). This means that
when you look at an existing pool it may have some space_maps
with histograms and ones without.
Thanks,
George
Post by aurfalien via illumos-zfsWow!
Thank you very much George, you are both a gentlemen and a
scholar to an order of magnitude!
I assume it best to implement on fresh pools to see the most benefits?
My path will most limey be to replicate on a system with it
enabled, then switch over to that system. Iâve 2 identical
servers for one of our main production resources.
- aurf
"Janitorial Services"
On Sep 10, 2014, at 8:04 AM, George Wilson
Post by George Wilson via illumos-zfsThe space_map histogram feature has been used in production
at Delphix for a while. The data it provide is being used
to make smarter decisions about how and where to allocate
blocks. It also gives us an idea of how badly fragmented
things get on a pool. For example, we've come up with a
simplistic metric to define pool fragmentation based on the
NAME SIZE ALLOC FREE EXPANDSZ FRAG CAP DEDUP
HEALTH ALTROOT
dcenter 8.22T 5.50T 2.71T - 53% 66% 1.00x
ONLINE -
The higher the frag% the more your free space is comprised
of small segments. We have been making many changes in this
area and more to come but the idea behind the histogram was
to be able to lay the foundation for improvements in
allocation strategies. You can take a closer look at the
histogram on your pool by running 'zdb -mm[m] <pool>'.
Hope this helps. I will try to get a more extensive write
up in a blog along with some of the perf enhancements we've
seen by making smarter allocations decisions. Unfortunately
right now I'm pretty busy with compressed ARC. If you have
more questions please feel free to ask (post or email
directly).
Thanks,
George
Post by aurfalien via illumos-zfsBy the way, any one know who George is?
Iâd like to ping him and see if he is satisfied yet ? :)
- aurf
"Janitorial Services"
On Sep 10, 2014, at 7:42 AM, aurfalien
Post by aurfalien via illumos-zfsHi Steven,
I gleaned this from an older Illumos post found here;
http://comments.gmane.org/gmane.os.illumos.zfs/2565
Of interest;
- There is a new spacemap_histogram on-disk feature flag.
When it is
enabled spacemaps store more data about the amount of
contiguous free
space in metaslabs. The current disk format only stores the total
amount of free space, which means that heavily fragmented
metaslabs
can look appealing, causing us to read them off disk,
even though they
don't have enough contiguous free space to satisfy large
allocations,
leading us to continually load the same fragmented space
maps over and
over again. The allocation algorithm that uses this
information is
disabled by default and can be enabled via a tunable. It
will become
the default allocator once George is satisfied with the amount of
performance testing it has received. We have extensively
tested this
code bo t h with the t unable enabled and disabled. It is
not possible to
seperate out spacemap_histogram from the rest of this refactoring
because they were done together.
- aurf
"Janitorial Services"
On Sep 10, 2014, at 7:36 AM, Steven Hartland
Post by Steven Hartland via illumos-zfsI've not used it I'm afraid as the man page provides no
real indication of what its benefit would be if used.
"This features allows ZFS to maintain more information
about how free space is organized within the pool.
Regards
Steve
----- Original Message ----- From: "aurfalien via
Sent: Wednesday, September 10, 2014 3:20 PM
Subject: [zfs] spacemap_histogram
Hi,
Iâve asked on the FreeBSD lists but no takers.
Curious if any one has tried the spacemap_histogram
feature in production.
Seems cool, in theory anyways.
Thanks in advance,
- aurf
"Janitorial Services"
-------------------------------------------
illumos-zfs
Archives: https://www.listbox.com/member/archive/182191/=now
https://www.listbox.com/member/archive/rss/182191/24401717-fdfe502b
Modify Your Subscription: https://www.listbox.com/member/?&
Powered by Listbox: http://www.listbox.com
<http://www.listbox.com/>
*illumos-zfs* | Archives
<https://www.listbox.com/member/archive/182191/=now>
<https://www.listbox.com/member/archive/rss/182191/22008002-303f2ff4>
| Modify <https://www.listbox.com/member/?&> Your
Subscription [Powered by Listbox] <http://www.listbox.com/>
*illumos-zfs* | Archives
<https://www.listbox.com/member/archive/182191/=now>
<https://www.listbox.com/member/archive/rss/182191/23654017-682fbee9>
| Modify <https://www.listbox.com/member/?&> Your
Subscription [Powered by Listbox] <http://www.listbox.com/>
--
Vadim Comanescu
Github: https://github.com/vadimcomanescu
Blog: http://vadimcomanescu.wordpress.com
<http://vadimcomanescu.wordpress.com/>
*illumos-zfs* | Archives
<https://www.listbox.com/member/archive/182191/=now>
<https://www.listbox.com/member/archive/rss/182191/24758408-e0240379>
| Modify
<https://www.listbox.com/member/?&>
Your Subscription [Powered by Listbox] <http://www.listbox.com/>
--
Vadim Comanescu
Github: https://github.com/vadimcomanescu
Blog: http://vadimcomanescu.wordpress.com
-------------------------------------------
illumos-zfs
Archives: https://www.listbox.com/member/archive/182191/=now
RSS Feed: https://www.listbox.com/member/archive/rss/182191/23047029-187a0c8d
Modify Your Subscription: https://www.listbox.com/member/?member_id=23047029&id_secret=23047029-2e85923f
Powered by Listbox: http://www.listbox.com