2016-01-07 7:03 GMT+01:00 Sitsofe Wheeler <sitsofe@xxxxxxxxx>: > Hi, > > On 6 January 2016 at 18:45, Jeff Furlong <jeff.furlong@xxxxxxxx> wrote: >> >> Here is 2.3 with a --runtime of 60s, and a runt of only 16s, and an error: >> >> # fio --name=SW_1MB_QD32 --ioengine=libaio --direct=1 --rw=write --iodepth=32 --size=1% --runtime=60s --time_based --numjobs=1 --bs=1m --overwrite=1 --filename=/dev/nvme0n1 >> SW_1MB_QD32: (g=0): rw=write, bs=1M-1M/1M-1M/1M-1M, ioengine=libaio, iodepth=32 >> fio-2.3-11-g5f3b >> Starting 1 process >> fio: io_u error on file /dev/nvme0n1: Invalid argument: write offset=153764, buflen=1048576 >> fio: io_u error on file /dev/nvme0n1: Invalid argument: write offset=1202340, buflen=1048576 >> fio: pid=68391, err=22/file:io_u.c:1596, func=io_u error, error=Invalid argument >> >> SW_1MB_QD32: (groupid=0, jobs=1): err=22 (file:io_u.c:1596, func=io_u error, error=Invalid argument): pid=68391: Wed Jan 6 08:48:18 2016 > > Can say how big /dev/nvme0n1 is and can you repeat your test but with > size set in bytes? I'm wondering if your 1MByte blocksize doesn't > divide evenly in the 1% space the job has to work with... Indeed I can pretty easily reproduce this by setting size to some odd value. git bisect then finds c82ea3d49aa as the culprit. -- To unsubscribe from this list: send the line "unsubscribe fio" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
