On Jun 01, 2022 / 20:32, Vincent Fu wrote: [...] > I ran > > t/zbd/run-tests-against-nullb > > and Test 1 ran for all sections. There were no test failures. > > I also created a zoned device with: > > modprobe scsi_debug zbc=2 zone_nr_conv=0 > > and then ran: > > t/zbd/test-zbd-support -l /dev/sg2 > > and all tests except Test 13 passed. The failure seems unrelated to this patch. The failure appears to be related to libzbc reporting max open zones incorrectly. I agree this test #13 failure has nothing to do with this change. I was able to recreate the test #13 failure in my test system. As far as I see, it is not related to libzbc, since it can be recreated with block device file without libzbc I/O engine. I found that the scsi_debug device created with the modprobe command above has very small max_open_zones attribute value '1'. The test case requires max_open_zones=4 or larger, then failed. By creating scsi_debug device with larger device size and larger number of zones, I observed the device has larger max_open_zones and the test case passes. Later on, I will post a patch to skip the test case for devices with max_open_zones smaller than 4. -- Shin'ichiro Kawasaki
