From 6fe3498ca3406ffb10f729ab4f9cf63f10c74ede Mon Sep 17 00:00:00 2001 From: Ryan Moeller Date: Fri, 21 Aug 2020 15:53:17 -0400 Subject: Import vdev ashift optimization from FreeBSD Many modern devices use physical allocation units that are much larger than the minimum logical allocation size accessible by external commands. Two prevalent examples of this are 512e disk drives (512b logical sector, 4K physical sector) and flash devices (512b logical sector, 4K or larger allocation block size, and 128k or larger erase block size). Operations that modify less than the physical sector size result in a costly read-modify-write or garbage collection sequence on these devices. Simply exporting the true physical sector of the device to ZFS would yield optimal performance, but has two serious drawbacks: 1. Existing pools created with devices that have different logical and physical block sizes, but were configured to use the logical block size (e.g. because the OS version used for pool construction reported the logical block size instead of the physical block size) will suddenly find that the vdev allocation size has increased. This can be easily tolerated for active members of the array, but ZFS would prevent replacement of a vdev with another identical device because it now appears that the smaller allocation size required by the pool is not supported by the new device. 2. The device's physical block size may be too large to be supported by ZFS. The optimal allocation size for the vdev may be quite large. For example, a RAID controller may export a vdev that requires read-modify-write cycles unless accessed using 64k aligned/sized requests. ZFS currently has an 8k minimum block size limit. Reporting both the logical and physical allocation sizes for vdevs solves these problems. A device may be used so long as the logical block size is compatible with the configuration. By comparing the logical and physical block sizes, new configurations can be optimized and administrators can be notified of any existing pools that are sub-optimal. Reviewed-by: Ryan Moeller Reviewed-by: Brian Behlendorf Co-authored-by: Matthew Macy Signed-off-by: Matt Macy Closes #10619 --- man/man5/zfs-module-parameters.5 | 23 +++++++++++++++++++++++ 1 file changed, 23 insertions(+) (limited to 'man/man5') diff --git a/man/man5/zfs-module-parameters.5 b/man/man5/zfs-module-parameters.5 index 463e51acc..853e8fc94 100644 --- a/man/man5/zfs-module-parameters.5 +++ b/man/man5/zfs-module-parameters.5 @@ -486,6 +486,29 @@ Default limit for metaslab size. Default value: \fB29\fR [meaning (1 << 29) = 512MB]. .RE +.sp +.ne 2 +.na +\fBzfs_vdev_max_auto_ashift\fR (ulong) +.ad +.RS 12n +Maximum ashift used when optimizing for logical -> physical sector size on new +top-level vdevs. +.sp +Default value: \fBASHIFT_MAX\fR (16). +.RE + +.sp +.ne 2 +.na +\fBzfs_vdev_min_auto_ashift\fR (ulong) +.ad +.RS 12n +Minimum ashift used when creating new top-level vdevs. +.sp +Default value: \fBASHIFT_MIN\fR (9). +.RE + .sp .ne 2 .na -- cgit v1.2.3