Hi all,
I'm recently reading fio source code and running it for test purpose.
A case bothered me which is fio keep going after posix_fallocate()
failed, I'm wondering why, shouldn't it abort immediately?
Information may be useful followed:
==part of the output==
fio: set debug option file
libaio.dat: (g=0): rw=randrw, bs=8K-8K/8K-8K/8K-8K, ioengine=libaio, iodepth=16
libaio.dat: Laying out IO file(s) (1 file(s) / 2048MB)
fio: posix_fallocate fails: No space left on device
fio: ENOSPC on laying out file, stopping
fio: io_u error on file /mnt/nfs/libaio.dat.1.0: No space left on device
write offset=1398325248, buflen=8192
fio: io_u error on file /mnt/nfs/libaio.dat.1.0: No space left on device
write offset=1994014720, buflen=8192
fio: pid=7152, err=28/file:io_u.c:1377, func=io_u error, error=No
space left on device
==reproduce==
dd if=/dev/zero of=/tmp/1gdisk bs=1M count=1024
losetup /dev/loop0 /tmp/1gdisk
mkfs.ext4 /dev/loop0
mount /dev/loop0 /mnt/loopfs
cat aio-bench # simplified here
// [global] ioengine=libaio,direct=1,rw=randrw,bs=8k,directory=/mnt/loopfs,time_based,runtime=10
// [libaio.dat] size=2g,iodepth=16
fio aio-bench
--
- Thanks.
- xan.peng
--
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
