diff options
author | Damien Le Moal <damien.lemoal@wdc.com> | 2019-08-29 16:21:33 +0900 |
---|---|---|
committer | Jens Axboe <axboe@kernel.dk> | 2019-08-29 06:30:49 -0600 |
commit | 402f08876d93be12f18703acfadb603eec7a5791 (patch) | |
tree | 9be513276d0386587a38f2290e60087ecb1a1a4d | |
parent | 4580ff92390da42c6a3026d787c6bc6c412af637 (diff) | |
download | fio-402f08876d93be12f18703acfadb603eec7a5791.tar.gz fio-402f08876d93be12f18703acfadb603eec7a5791.tar.bz2 |
man page: Fix read_beyond_wp description
Strictly speaking, drive managed disks are not zoned block devices as
they do not provide zone information nor zone commands. So remove
mention of this type of disk in the zoned block device description.
Signed-off-by: Damien Le Moal <damien.lemoal@wdc.com>
Signed-off-by: Jens Axboe <axboe@kernel.dk>
-rw-r--r-- | fio.1 | 8 |
1 files changed, 4 insertions, 4 deletions
@@ -778,10 +778,10 @@ Zoned block devices are block devices that consist of multiple zones. Each zone has a type, e.g. conventional or sequential. A conventional zone can be written at any offset that is a multiple of the block size. Sequential zones must be written sequentially. The position at which a write must occur is -called the write pointer. A zoned block device can be either drive -managed, host managed or host aware. For host managed devices the host must -ensure that writes happen sequentially. Fio recognizes host managed devices -and serializes writes to sequential zones for these devices. +called the write pointer. A zoned block device can be either host managed or +host aware. For host managed devices the host must ensure that writes happen +sequentially. Fio recognizes host managed devices and serializes writes to +sequential zones for these devices. If a read occurs in a sequential zone beyond the write pointer then the zoned block device will complete the read without reading any data from the storage |