[PATCH blktests 0/2] nvme: avoid failures of TEST_DEV with metadata

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Recently, the new test case nvme/064 was introduced to cover namespaces
formatted with metadata [1]. To run the test case, it is required to
specify namespaces with metadata as TEST_DEV. When this TEST_DEV is used
for other test cases, a few other test cases fail. This series addresses
the failures. The first patch allows skipping nvme/034 and nvme/035 when
TEST_DEV has metadata. The second patch adds an option to the fio
command in nvme/049 that is required for TEST_DEV with metadata.

[1] https://lore.kernel.org/linux-nvme/20250616020716.2789576-1-shinichiro.kawasaki@xxxxxxx/

P.S. I had observed nvme/053 failure using TEST_DEV with metadata, but
     it was because I configured QEMU NVME namespace as TEST_DEV with
     512b block size. With 4k block size, the failure disappeared.


Shin'ichiro Kawasaki (2):
  nvme/{034,035}: skip when the test target namespace has metadata
  nvme/049: add fio md_per_io_size option

 tests/nvme/034 |  1 +
 tests/nvme/035 |  1 +
 tests/nvme/049 | 13 +++++++++++++
 tests/nvme/rc  |  8 ++++++++
 4 files changed, 23 insertions(+)

-- 
2.49.0





[Index of Archives]     [Linux RAID]     [Linux SCSI]     [Linux ATA RAID]     [IDE]     [Linux Wireless]     [Linux Kernel]     [ATH6KL]     [Linux Bluetooth]     [Linux Netdev]     [Kernel Newbies]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Device Mapper]

  Powered by Linux