Others could probably answer, but in the meantime could you try changing the 512B bssplit to 4K? I admit it's a bit of a swag... Tim Walker Systems Engineering > On May 30, 2016, at 9:37 AM, Nitin Mathur <nitinmathur@xxxxxxxxx> wrote: > > I am getting the following error and need help from someone > > Test environment > CentOS 6.5 > Linux kernel: 3.8.8, 64 bit > FIO version: fio-2.11 > > I run the following command > >> ./fio --name=test_workld --ioengine=libaio --direct=1 --rw=randrw --norandommap --randrepeat=0 --rwmixread=40 --rwmixwrite=60 --iodepth=256 --size=100% --numjobs=4 --bssplit=512/4:64k/96 --random_distribution=zoned:50/5:50/95 --overwrite=1 --output=test_op --filename=/dev/nvme0n1 --group_reporting --runtime=1m --time_based > > > This means, I'm using libaio, with a queue depth of 256, and fio is > utilizing asynchronous IO engines. But when i run this command, it > results into an error "Invalid argument". If i change the parameter > --direct=0, I'm able to issue the command successfully. > > Can you help me to understand, why with direct=1, the fio command > results in an error ? > > Thanks > Nitin > -- > To unsubscribe from this list: send the line "unsubscribe fio" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at https://urldefense.proofpoint.com/v2/url?u=http-3A__vger.kernel.org_majordomo-2Dinfo.html&d=CwIDaQ&c=IGDlg0lD0b-nebmJJ0Kp8A&r=NW1X0yRHNNEluZ8sOGXBxCbQJZPWcIkPT0Uy3ynVsFU&m=iq608km1yBu7HmXRbaOtJbbsTztTq7_DHpO8EmfutZU&s=SKPO5VaH1JwEZGe0QKLLDQOCy6njnE5FT-DYzNRDWBQ&e= -- 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
