I have run fio without verify and this issue didn't happen. So it should be verify issue. The fio job file is as below: [global] thread=1 invalidate=1 rw=randwrite time_based=1 runtime=3000 rwmixread=50 ioengine=libaio direct=1 bs=4096 iodepth=16 verify_dump=1 verify_async=10 do_verify=1 verify=meta verify_pattern="meta" [job0] filename=/dev/sda [job1] filename=/dev/sdb I think you can use ram disk(ubuntu have ram disk /dev/ram*) to reproduce this issue. It happened with devices which have high speed. 2016-03-23 8:42 GMT+08:00 Jens Axboe <axboe@xxxxxxxxx>: > What job did you run? When reporting a potential issue, always include that. Hard to help or advise otherwise. > >> On Mar 22, 2016, at 5:12 PM, flash yan <flashyan83@xxxxxxxxx> wrote: >> >> This issue happened after about 20 minutes. The iscsi device is very >> small, only 128MB. >> As you said, I have enabled verify= options. >> I will try big iscsi device and no verify. >> >> Thanks >> >> Liang Yan >> >> 2016-03-23 0:30 GMT+08:00 Jens Axboe <axboe@xxxxxxxxx>: >>>> On 03/22/2016 08:06 AM, flash yan wrote: >>>> >>>> Hi all, >>>> >>>> I have run fio-2.7 to test iscsi device, one unusual issue happened. >>>> If I set the io_size to 4096, queue_depth to 16 ,rw to randwrite and >>>> run_time to 3000, >>>> the fio would invoke oom_killer and the Linux OS would kill the fio >>>> process. >>>> The machine have about 11 GB memory and I have tried the machine with >>>> 23GB, the issue also happened. >>>> I think fio have problem when dealing with 4KB io_size then used too >>>> many memory. >>> >>> >>> When did this happen - shortly after the job is started, or long after? How >>> big is the iscsi device? Did you have verify= options enabled? >>> >>> -- >>> Jens Axboe >>> -- 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
