On 2/1/24 16:48, Amir Goldstein wrote:
> On Thu, Feb 1, 2024 at 5:43 PM Miklos Szeredi <miklos@xxxxxxxxxx> wrote:
>>
>> On Thu, 1 Feb 2024 at 16:40, Bernd Schubert <bschubert@xxxxxxx> wrote:
>>
>>> Given
>>> -N numops: total # operations to do (default infinity)
>>>
>>> How long do you think I should run it? Maybe something like 3 hours
>>> (--duration=$(3 * 60 * 60))?
>>
>> I used -N1000000. If there were any issues they usually triggered much earlier.
>>
>
> Note that at least these fstests run fsx in several configurations:
>
> $ grep begin `git grep -l run_fsx tests/generic/`
> tests/generic/091:_begin_fstest rw auto quick
> tests/generic/263:_begin_fstest rw auto quick
> tests/generic/469:_begin_fstest auto quick punch zero prealloc
> tests/generic/521:_begin_fstest soak long_rw smoketest
> tests/generic/522:_begin_fstest soak long_rw smoketest
> tests/generic/616:_begin_fstest auto rw io_uring stress soak
> tests/generic/617:_begin_fstest auto rw io_uring stress soak
>
> Bernd, you've probably already ran them if you are running auto, quick
> or rw test groups.
>
> Possibly you want to try and run also the -g soak.long_rw tests.
>
> They use nr_ops=$((1000000 * TIME_FACTOR))
I didn't check yet what is the actual value, but TIME_FACTOR must be
smaller than 1 - using "-N1000000" is taking quite some time. I should
have started in screen. Some of the tests are marked as failed, like
generic/263:
+main: filesystem does not support fallocate mode
FALLOC_FL_KEEP_SIZE, disabling!
+main: filesystem does not support fallocate mode
FALLOC_FL_PUNCH_HOLE | FALLOC_FL_KEEP_SIZE, disabling!
+main: filesystem does not support fallocate mode
FALLOC_FL_ZERO_RANGE, disabling!
Although the test runs
generic/469 7s ... [not run] xfs_io falloc -k failed (old kernel/wrong fs?)
generic/521
generic/522
--> Somehow not in the output list at all. Ah I see, that needs "-g
soak.long_rw"
Going to add the the soak.long option to the tests and will run again,
once current fsx is over.
Thanks,
Bernd
