[bug report] blktests nvme/tcp nvme/014 failed due to Read/Flush timeout

[Daniel Wagner]

On Mon, Apr 22, 2024 at 12:55:33PM +0800, Yi Zhang wrote:
> I found nvme/014 failed[1] on one of my servers, seems it was due to
> Read/Flush timeout during the test[2], I tried to add sync operation
> after the dd operation[3] and the failure can be fixed now and no
> timeout from dmesg, could anyone help check if it's one test issue or
> nvme/tcp stack issue, thanks.

>From your log I'd say the sync command is just timing out too early. The
write operations are just too slow. Not really sure what the test is
suppose to test here. Should it test if the flush works or if the flush
is flushing any pending I/O? In the first case, the sync would be the
right fix. In the second case I suppose we would need to consider how
log it takes to flush pending I/Os and extend the timeout accordingly?

Thoughs?