On 7/28/18 6:11 AM, Ming Lei wrote: > On Fri, Jul 27, 2018 at 11:47 PM, Josef Bacik <josef@xxxxxxxxxxxxxx> wrote: >> On Sun, Jul 22, 2018 at 03:28:05PM +0800, Ming Lei wrote: >>> On Sun, Jul 22, 2018 at 02:15:38AM +0000, Josef Bacik wrote: >>>> Yup I sent a patch for this on Thursday, sorry about that, >>>> >>> >>> I just applied the patch of 'blk-rq-qos: make depth comparisons unsigned', >>> looks the same IO hang can be triggered too. >> >> Ok I'm back from vacation and I'm trying to reproduce but it's not happening for >> me. What testing infrastructure is this? blktests and xfstests don't have a >> sanity/ in their test suites. I'm wondering if there's something else about the >> test that I'm missing. Thanks, > > As I mentioned, > > The following IO hang is triggered on dbench test on xfs/usb-storage: > > dbench -t 20 -s 64 Josef, the key here is likely a queue depth of 1. So if you're running on sata, then just limit the device depth to 1. -- Jens Axboe
