mirror_zfs/man
Paul Dagnelie 2adca179b6 Expand fragmentation table to reflect larger possibile allocation sizes
When you are using large recordsizes in conjunction with raidz, with
incompressible data, you can pretty reliably be making 21 MB
allocations. Unfortunately, the fragmentation metric in ZFS considers
any metaslabs with 16 MB free chunks completely unfragmented, so you can
have a metaslab report 0% fragmented and be unable to satisfy an
allocation. When using the segment-based metaslab weight, this is
inconvenient; when using the space-based one, it can seriously degrade
performance.

We expand the fragmentation table to extend up to 512MB, and redefine
the table size based on the actual table, rather than having a static
define. We also tweak the one variable that depends on fragmentation
directly.

Sponsored-by: Klara, Inc.
Sponsored-by: Wasabi Technology, Inc.
Reviewed-by: Allan Jude <allan@klarasystems.com>
Reviewed-by: Alexander Motin <mav@FreeBSD.org>
Signed-off-by: Paul Dagnelie <paul.dagnelie@klarasystems.com>
Closes #16986
2025-02-28 00:42:29 +05:00
..
man1 arcstat: add structural, types, states breakdown 2024-09-18 11:44:18 -07:00
man4 Expand fragmentation table to reflect larger possibile allocation sizes 2025-02-28 00:42:29 +05:00
man5 vdev_id: multi-lun disks & slot num zero pad 2024-10-09 13:44:55 -07:00
man7 Fix several typos in the man pages 2025-02-25 22:27:47 +05:00
man8 Clarify documentation of zfs destroy on snapshots (#17021) 2025-02-28 00:42:29 +05:00
Makefile.am Add DDT prune command 2024-09-04 14:17:02 -07:00