> -----Original Message----- > From: Jens Axboe [mailto:axboe@xxxxxxxxx] ... > I'd much rather keep fio ignorant of any "special" directories, even if > it means that sometimes you do potentially run into issues like the > above, where you specify a block device that does not exist. How about an option in the script: direct=2 file must exist and be a block device, otherwise skip it If the size is too big, this is the error: drive_r: Laying out IO file(s) (1 file(s) / 1572864000MB) fio: posix_fallocate fails: No space left on device fio: ENOSPC on laying out file, stopping fio: looks like your file system does not support direct=1/buffered=0 fio: destination does not support O_DIRECT fio: looks like your file system does not support direct=1/buffered=0 fio: destination does not support O_DIRECT fio: pid=8991, err=22/file:filesetup.c:611, func=open(/dev/sdnothere), error=Invalid argument fio: pid=8990, err=22/file:filesetup.c:611, func=open(/dev/sdnothere), error=Invalid argument and it leaves a "file" that looks like: $ ls -alt /dev/sd* -rw-r--r-- 1 root root 1649267441664000 Sep 30 20:10 /dev/sdnothere ��.n��������+%������w��{.n�������^n�r������&��z�ޗ�zf���h���~����������_��+v���)ߣ�
