On 23.12.21 17:53, Hanna Reitz wrote:
This test assumes that mirror flushes the source when entering the READY
state, and that the format level will pass that flush on to the protocol
level (where we intercept it with blkdebug).
However, apparently that does not happen when using a VMDK image wi
On 23.12.21 18:50, Vladimir Sementsov-Ogievskiy wrote:
23.12.2021 19:53, Hanna Reitz wrote:
This test assumes that mirror flushes the source when entering the READY
state, and that the format level will pass that flush on to the protocol
level (where we intercept it with blkdebug).
However, app
23.12.2021 20:50, Vladimir Sementsov-Ogievskiy wrote:
Hmm, relying on flush requests sequence doesn't seem reliable..
Maybe, it's better to insert blockdev-add filter after JOB_READY? blockdev-reopen should
work now for "file" link changing.
s/blockdev-add/blkdebug/ :)
--
Best regards,
Vladi
23.12.2021 19:53, Hanna Reitz wrote:
This test assumes that mirror flushes the source when entering the READY
state, and that the format level will pass that flush on to the protocol
level (where we intercept it with blkdebug).
However, apparently that does not happen when using a VMDK image wit
This test assumes that mirror flushes the source when entering the READY
state, and that the format level will pass that flush on to the protocol
level (where we intercept it with blkdebug).
However, apparently that does not happen when using a VMDK image with
zeroed_grain=on, which actually is th
