On 7 February 2018 at 00:19, Gnana Sekhar <kgsgnana2020@xxxxxxxxx> wrote: > > Experimented few loops and ran into the below failures even when I > didn't pass in the write offset to FIO. The block size is 4k on the > drive > > 2018-02-05 07:20:53,033-07 ERROR l_IoActionsLinux - The arguments > passed are: sudo fio --thread --direct=1 --minimal --ioengine=libaio > --numjobs=1 --filename=/dev/nvme0n1 -o /tmp/nvme0n1_temp.log > --name=bs16384_rwwrite_qd256 --buffer_pattern=1193046 --iodepth=256 > --size=100% --percentage_random=0 --bs=256k --ba=4k --rw=write > 2018-02-05 07:20:53,033-07 ERROR l_IoActionsLinux - Error in FIO > run: fio: io_u error on file /dev/nvme0n1: Input/output error: write > offset=27160215552, buflen=262144 > > 2018-02-05 07:20:53,033-07 ERROR l_IoActionsLinux - Error in FIO > run: fio: io_u error on file /dev/nvme0n1: Input/output error: write > offset=27205828608, (note that blockalign/ba is only really for random I/O) This looks strange. What does blockdev --getsize64 /dev/nvme0n1 report and is there anything interesting in the tail end of dmesg just after you trigger this issue? > Similarly if I pass offsets that aren't aligned with file system > underneath, is there a way to inform fio to round it up Jeff answered this one in another reply. -- Sitsofe | http://sucs.org/~sits/ -- 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
