block test failure with scsi_debug

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

 



Hi,

I found few failures, are you also getting the same ?

linux-block/for-next observed block test failure :-

blktests (master) # ./check block
block/001 (stress device hotplugging) [failed]
     runtime  42.992s  ...  0.060s
     --- tests/block/001.out    2022-07-18 16:14:37.194229987 -0700
     +++ /root/blktests/results/nodev/block/001.out.bad 2023-06-19 
23:07:11.960344657 -0700
     @@ -1,4 +1,6 @@
      Running block/001
      Stressing sd
     +modprobe: FATAL: Module scsi_debug is in use.
      Stressing sr
     +modprobe: FATAL: Module scsi_debug is in use.
      Test complete
block/002 (remove a device while running blktrace) [failed]
     runtime  1.176s  ...  0.033s
     --- tests/block/002.out    2022-07-18 16:14:37.194229987 -0700
     +++ /root/blktests/results/nodev/block/002.out.bad 2023-06-19 
23:07:12.037346576 -0700
     @@ -1,2 +1,2 @@
      Running block/002
     -Test complete
     +modprobe: FATAL: Module scsi_debug is in use.
block/006 (run null-blk in blocking mode) [passed]
     read iops  9950112  ...  9721038
     runtime    8.605s   ...  8.796s
block/007 => nullb1 (test classic and hybrid IO polling) [passed]
     auto hybrid poll read iops       789590      ...  780190
     auto hybrid poll read lat mean   1.053785    ...  1.071952
     auto hybrid poll system cpu      75.226586%  ...  74.626866%
     classic poll read iops           784862      ...  791975
     classic poll read lat mean       1.060873    ...  1.050524
     classic poll system cpu          73.273273%  ...  68.787879%
     fixed hybrid poll read iops      789590      ...  784862
     fixed hybrid poll read lat mean  1.055413    ...  1.063116
     fixed hybrid poll system cpu     68.580060%  ...  73.873874%
     no poll read iops                768750      ...  780190
     no poll read lat mean            1.084178    ...  1.067840
     no poll system cpu               74.411765%  ...  72.835821%
     runtime                          2.152s      ...  2.160s
block/009 (check page-cache coherency after BLKDISCARD) [failed]
     runtime  0.417s  ...  0.004s
     --- tests/block/009.out    2022-07-18 16:14:37.195230012 -0700
     +++ /root/blktests/results/nodev/block/009.out.bad 2023-06-19 
23:07:23.544615767 -0700
     @@ -1,8 +1,2 @@
      Running block/009
     -0000000 0000 0000 0000 0000 0000 0000 0000 0000
     -*
     -2000000
     -0000000 0000 0000 0000 0000 0000 0000 0000 0000
     -*
     -2000000
     ...
     (Run 'diff -u tests/block/009.out 
/root/blktests/results/nodev/block/009.out.bad' to see the entire diff)
block/010 (run I/O on null_blk with shared and non-shared tags) [passed]
     Individual tags read iops  9018796  ...  8652509
     runtime                    18.806s  ...  19.036s
     Shared tags read iops      8705261  ...  8738133
block/014 (run null-blk with blk-mq and timeout injection configured) 
[not run]
     null_blk module does not have parameter timeout
block/015 (run null-blk on different schedulers with requeue injection 
configured) [not run]
     null_blk module does not have parameter requeue
block/016 (send a signal to a process waiting on a frozen queue) [passed]
     runtime  7.074s  ...  7.080s
block/017 (do I/O and check the inflight counter) [passed]
     runtime  1.839s  ...  1.843s
block/018 (do I/O and check iostats times) [passed]
     runtime  5.109s  ...  5.106s
block/020 (run null-blk on different schedulers with only one hardware 
tag) [passed]
     runtime  31.049s  ...  31.043s
block/021 (read/write nr_requests on null-blk with different schedulers) 
[passed]
     runtime  3.907s  ...  3.983s
block/022 (Test hang caused by freeze/unfreeze sequence) [passed]
     runtime  30.130s  ...  30.163s
block/023 (do I/O on all null_blk queue modes) [passed]
     runtime  0.223s  ...  0.224s
block/024 (do I/O faster than a jiffy and check iostats times) [passed]
     runtime  2.609s  ...  2.593s
block/025 (do a huge discard with 4k sector size) [failed]
     runtime  0.004s  ...  0.004s
     --- tests/block/025.out    2022-07-18 16:14:37.196230036 -0700
     +++ /root/blktests/results/nodev/block/025.out.bad 2023-06-19 
23:09:05.705043001 -0700
     @@ -1,2 +1,2 @@
      Running block/025
     -Test complete
     +modprobe: FATAL: Module scsi_debug is in use.
block/027 (stress device hotplugging with running fio jobs and different 
schedulers) [failed]
     runtime  0.003s  ...  0.028s
     --- tests/block/027.out    2022-07-18 16:14:37.196230036 -0700
     +++ /root/blktests/results/nodev/block/027.out.bad 2023-06-19 
23:09:05.858046859 -0700
     @@ -1,2 +1,3 @@
      Running block/027
     +modprobe: FATAL: Module scsi_debug is in use.
      Test complete
block/028 (do I/O on scsi_debug with DIF/DIX enabled) [failed]
     runtime  0.022s  ...  0.025s
     --- tests/block/028.out    2022-07-18 16:14:37.196230036 -0700
     +++ /root/blktests/results/nodev/block/028.out.bad 2023-06-19 
23:09:05.938048876 -0700
     @@ -1,9 +1,17 @@
      Running block/028
     +modprobe: FATAL: Module scsi_debug is in use.
      Test(dix:0 dif:0) complete
     +modprobe: FATAL: Module scsi_debug is in use.
      Test(dix:0 dif:1) complete
     +modprobe: FATAL: Module scsi_debug is in use.
      Test(dix:0 dif:2) complete
     ...
     (Run 'diff -u tests/block/028.out 
/root/blktests/results/nodev/block/028.out.bad' to see the entire diff)
block/029 (trigger blk_mq_update_nr_hw_queues()) [passed]
     runtime  3.207s  ...  30.284s
block/030 (trigger the blk_mq_realloc_hw_ctxs() error path)  [not run]
     null_blk module does not have parameter init_hctx
block/031 (do IO on null-blk with a host tag set) [passed]
     runtime  1.591s  ...  30.319s
block/032 (remove one mounted device) [failed]
     runtime  0.003s  ...  0.003s
     --- tests/block/032.out    2023-02-15 11:34:00.856501947 -0800
     +++ /root/blktests/results/nodev/block/032.out.bad 2023-06-19 
23:10:06.986538463 -0700
     @@ -1,2 +1,2 @@
      Running block/032
     -Test complete
     +modprobe: FATAL: Module scsi_debug is in use.
block/033 (add & delete ublk device and test if gendisk is leaked) [not run]
     miniublk was not built; run `make`
block/034 (load/unload null_blk memory_backed=1 to check memleak) [failed]
     runtime    ...  0.940s
     --- tests/block/034.out    2023-06-19 23:07:02.496108712 -0700
     +++ /root/blktests/results/nodev/block/034.out.bad 2023-06-19 
23:10:08.026563451 -0700
     @@ -1,2 +1,3 @@
      Running block/034
     +Memleak: Memory is not freed by null-blk driver
      Test complete


-ck





[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