Re: Corrupted json file

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,

On 4 September 2017 at 10:29, Udi-Yehuda Tamar <udi@xxxxxxxxxxxx> wrote:
>
> we're using the latest stable 2.99GA FIO for our product testing ,
> when trying to setup fio to write on ext4 mount we got a line that
> failing our code to load the json file .
> mt exe cmd:
>
> fio --verify=md5 --randrepeat 0 --direct=1 --rw write --thread=32

Thread doesn't take a parameter (see
http://fio.readthedocs.io/en/latest/fio_doc.html#cmdoption-arg-thread
)...

>  --exitall_on_error=1 --directory /mnt/v1 --verify_interval=4096
> --buffered 0 --output-format=json --size 1M --iodepth 1 --name FioJob
> --rwmixread 100 --verify_dump=1 --norandommap --verify_fatal=1
> --output /var/opt/executions/None/FioFS_f12f9c_1504448587_None.log
> --runtime 0 --fill_fs 0 --do_verify=1 --numjobs 20 --blocksize 4K
> --verify_pattern=0xaa --time_based=0 --ioengine libaio
>
>
> output file:
>
> Multiple writers may overwrite blocks that belong to other jobs. This
> can cause verification failures.

Does git fio still generate this warning? If it's gone it mean the
general problem of warnings interfering with json has been solved but
it might mean you don't trigger that particular warning with this
particular job...

-- 
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



[Index of Archives]     [Linux Kernel]     [Linux SCSI]     [Linux IDE]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux SCSI]

  Powered by Linux