Sitsofe Wheeler

@tmdrod can you reproduce in the latest fio (we only support the latest)? See https://github.com/axboe/fio/releases for which version we're up to.

Closing due to lack of reply from reporter. If this issue is still happening with the latest fio (see https://github.com/axboe/fio/releases to find out which version that is) please reopen. Thanks!

It looks like `read_iolog2()` in [iolog.c](https://github.com/axboe/fio/blob/a3e33e2fc06582e4170f90ae6e62d6225d52dc7c/iolog.c#L476-L493) is missing the case for trim. It's a bit tricky because a replay need not match that workloads in https://github.com/axboe/fio/blob/a3e33e2fc06582e4170f90ae6e62d6225d52dc7c/io_ddir.h#L42-L43 . Probably the easiest...

(You can check if systemd-timesyncd has synchronized (assuming you are actually using it and not some other time sync server that implements the timedate DBUS interface such as chrony) by...

@fabiand Perhaps you could build a new project called multipath-libiscsi library that would take care of the multipathing using different libiscsi connections? The problem is multipathing is a big job...

@ddis One additional point is that it looks like the target has to have the Type Mask Valid bit set to one before you can ask what's supported otherwise you...

@clicx could you include a backtrace and confirm that you're on the latest git version of libiscsi?

@clicx OK so latest git. In terms of backtrace I meant like the `thread apply all bt` output you get from GDB (e.g. see https://wiki.debian.org/HowToGetABacktrace ).

@clicx can you tell us which platform you're using libiscsi on?

@clicx Also does https://github.com/sahlberg/libiscsi/blob/e0fd6dc05156f467bffc035be91ea56100b268fa/tests/prog_reconnect_timeout.c work for you?