On Tue, Feb 02, 2021 at 02:22:53PM +0800, Zorro Lang wrote: > This case print both fio stdout and stderr to .full file, that cause > we miss some unexpected failures when there's a bug. For example: > > file:io_u.c:1803, func=io_u error, error=Block device required > > This's an regression issue we find on a downstream kernel, not in > upstream. So release unexpected fio error output to find more issues. > > Signed-off-by: Zorro Lang <zlang@xxxxxxxxxx> > --- Seems reasonable: Reviewed-by: Brian Foster <bfoster@xxxxxxxxxx> > tests/generic/095 | 5 ++++- > 1 file changed, 4 insertions(+), 1 deletion(-) > > diff --git a/tests/generic/095 b/tests/generic/095 > index 9afaa761..30fe77a5 100755 > --- a/tests/generic/095 > +++ b/tests/generic/095 > @@ -98,8 +98,11 @@ _require_fio $fio_config > _scratch_mkfs >>$seqres.full 2>&1 > _scratch_mount > > +# There's a known EIO failure to report collisions between directio and buffered > +# writes to userspace, refer to upstream linux 5a9d929d6e13. So ignore EIO error > +# at here. > +$FIO_PROG $fio_config --ignore_error=,EIO --output=$seqres.full > echo "Silence is golden" > -$FIO_PROG $fio_config >>$seqres.full 2>&1 > > # xfs generates WARNINGs on purpose when applications mix buffered/mmap IO with > # direct IO on the same file. On the other hand, this fio job has been proven > -- > 2.29.2 >
