On 01/24/2017 11:06 PM, Jens Axboe wrote: > On 01/24/2017 12:55 PM, Jens Axboe wrote: >> Try this patch. We only want to bump it for the driver tags, not the >> scheduler side. > > More complete version, this one actually tested. I think this should fix > your issue, let me know. > Nearly there. The initial stall is gone, but the test got hung at the 'stonewall' sequence again:
[global] bs=4k ioengine=libaio iodepth=256 size=4g direct=1 runtime=60 # directory=/mnt numjobs=32 group_reporting cpus_allowed_policy=split filename=/dev/md127 [seq-read] rw=read -> stonewall [rand-read] rw=randread stonewall Restarting all queues made the fio job continue. There were 4 queues with state 'restart', and one queue with state 'active'. So we're missing a queue run somewhere. Cheers, Hannes -- Dr. Hannes Reinecke Teamlead Storage & Networking h...@suse.de +49 911 74053 688 SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg GF: F. Imendörffer, J. Smithard, J. Guild, D. Upmanyu, G. Norton HRB 21284 (AG Nürnberg) -- To unsubscribe from this list: send the line "unsubscribe linux-block" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
