The zoned block device (ZBD) interface supporting ZBC and ZAC disks was added to Linux® kernel version 4.10. All Linux kernel versions since 4.10 include the ZBD interface.
Linux kernels prior to version 4.10 do not have the ZBD interface implemented. As a result of using such older kernel, access and management of ZBC and ZAC disks will be limited but still possible. This is discussed in more details in the Linux Support document.
In addition to a correct Linux kernel version, several user utilities should be installed on the test system to easily verify if the zoned device is discovered and initialized correctly.
A system with a Linux kernel version 4.10 or higher is recommended to get started with ZBC and ZAC hard disks. For a quick start, it is recommended to use a Linux distribution including ZBD support. More information on recommended Linux distributions can be found here.
Advanced users may want to compile and install a specific Linux kernel version to be used in place of the default kernel shipped with the distribution being used. Instructions on how to enable ZBD support in the kernel configuration are provided here. It is recommended to always use the highest available stable kernel version, or a long term stable kernel version higher than 4.10. Information on available kernel versions can be found here.
Kernel Version and ZBD Support
Two conditions must be met to ensure that a system Linux kernel supports the ZBD interface.
The kernel version must be 4.10.0 or higher,
The kernel compilation configuration option CONFIG_BLK_DEV_ZONED must be enabled.
The command uname allows checking the version of the kernel running on a system. For example, on a Fedora 29 distribution, this command output is as follows.
# uname -r 5.0.13-200.fc29.x86_64
Zoned Block Device Support
Zoned block device support is optional and may not be enabled in the running kernel. The kernel configuration option enabling zoned block device support is CONFIG_BLK_DEV_ZONED.
To check if the CONFIG_BLK_DEV_ZONED option is enabled for the kernel, several
method can be used. Not all method may work for a particular distribution.
In many cases, the configuration file for the running kernel can be found under
/boot directory and/or within the directory containing the kernel modules.
In such case, the following commands allow testing if the installed kernel supports zoned block devices.
# cat /boot/config-`uname -r` | grep CONFIG_BLK_DEV_ZONED CONFIG_BLK_DEV_ZONED=y
# cat /lib/modules/`uname -r`/config | grep CONFIG_BLK_DEV_ZONED CONFIG_BLK_DEV_ZONED=y
If the output of one of these commands is
CONFIG_BLK_DEV_ZONED=y, then zoned
block devices are supported by the kernel. If the output is
CONFIG_BLK_DEV_ZONED=n, then block device support is disabled and the kernel
needs to be recompiled.
For kernels older than kernel version 4.10, the output of these commands is always empty.
For kernels exporting the configuration through the proc file system, the following command can also be used.
# modprobe configs # cat /proc/config.gz | gunzip | grep CONFIG_BLK_DEV_ZONED CONFIG_BLK_DEV_ZONED=y
# modprobe configs # zcat /proc/config.gz | grep CONFIG_BLK_DEV_ZONED CONFIG_BLK_DEV_ZONED=y
Write Ordering Control
By default, Linux kernel does not provide any guarantee on the order in which commands are delivered to a block device. That is, an application writing sequentially to a disk may see write commands being delivered to the disk in a different order. This can cause write errors when writing to a zoned device sequential zones.
To avoid this problem, a zone write lock mechanism serializing writes to sequential zones is implemented by all kernels supporting zoned block devices. For kernel versions between 4.10 and 4.15 included, no special configuration is necessary and the kernel will provide guarantees that write commands are delivered to the device in the same order as the application write requests issuing order.
However, starting with kernel version 4.16, zone write locking implementation was moved to the deadline and mq-deadline block I/O scheduler. Using this scheduler with zoned block devices is mandatory to ensure write command order guarantees.
The mq-deadline block I/O scheduler is enabled only if the SCSI multi-queue (scsi-mq) infrastructure is enabled. This feature use can be controlled using the kernel boot argument scsi_mod.use_blk_mq". scsi-mq* is the default since kernel version 5.0 and the legacy single queue SCSI command path is no longer supported.
To verify the block I/O scheduler of a zoned disk, the following command can be used.
# cat /sys/block/sdb/queue/scheduler [none] mq-deadline kyber bfq
If the disk block I/O scheduler selected is not mq-deadline as in the example above, the scheduler can be changed with the following command.
# echo deadline > /sys/block/sdb/queue/scheduler # cat sys/block/sdb/queue/scheduler [mq-deadline] kyber bfq none
Various user level tools should also be installed in order to verify the correct operation of zoned block devices and to troubleshoot problems.
The lsblk command in Linux lists block devices, including zoned block devices. This utility is generally packaged as part of the util-linux package which is installed by default on most Linux distributions.
lsblk usage examples are provided here.
Similarly to the
lsblk utility, the
blkzone utility is another program
generally packaged as part of the util-linux package. This utility allows
listing (reporting) the zones of a zoned block device and to reset the write
pointer position of a range of zones of the device.
blkzone usage examples are provided here.
The lsscsi command lists information about the SCSI devices connected to a Linux system. lsscsi is generally available as a package with most Linux distributions. Refer to your distribution documentation to find out the name of the package providing the lsscsi utility.
The linux utilities page provides more information and usage examples.
The sg3_utils package is a collection of command line tools that send SCSI commands to a SCSI device.
Since in Linux all disks are exposed as SCSI disks, including all ATA drives, these utilities can be used to manage both SAS ZBC disks and SATA ZAC disks. For SATA disks connected to SATA ports (e.g. An AHCI adapter), the kernel SCSI subsystem translates SCSI commands to ATA commands.
sg3_utils includes three command line tools specific to ZBC disks.
|Utility Name||SCSI Command Invoked||Description|
|sg_rep_zones||REPORT ZONES||Get a ZBC disk zone information|
|sg_reset_wp||RESET WRITE POINTER||Reset one or all zones of ZBC disk|
|sg_zone||CLOSE ZONE, FINISH ZONE, OPEN ZONE||Sends one of these commands to the given ZBC disk|
This section shows some examples of these utilities execution
libzbc is a user space library providing functions for manipulating ZBC and ZAC disks. The libzbc project is hosted on GitHub. Documentation is provided in the project README file. The API documentation can also be automatically generated using doxygen.
libzbc also provides a set of command line utilities with similar
functionalities as the
blkzone utility and the sg3_utils command line tools.
More information on how to compile and install libzbc as well as usage examples of the command line utilities provided can be found here.