On Mon, 09 Nov 2026 20:06:01 +0100, Denis V. Lunev wrote:
> dm-ploop: fix writes to a read-only device hanging the host
>
> A write that reaches a read-only ploop device never completes: the
> writer hangs in D state, and after a buffered write every later sync on
> the host hangs behind it until a reboot. Such writes come from a device
> stacked on top. libploop leaves the partition of "ploop mount -r"
> writable, which the ploop side fixes in openvz/ploop.ovz PR 513, and
> libvzctl attaches a backup disk to a Container that way and mounts it
> read-write (VSTOR-154096).
>
> [...]
Applied to branch-rh10-6.12.0-211.52.1.22.x.vz10-ovz, will be released in
rh10-6.12.0-211.52.1.22.20.vz10, thanks!
[1/3] dm-ploop: factor out ploop_dispatch_md_waiters()
https://bitbucket.org/virtuozzocore/vzkernel.vzs/commits/f63736a643a0
[2/3] dm-ploop: fix pios stuck in md->wait_llist after a failed BAT update
https://bitbucket.org/virtuozzocore/vzkernel.vzs/commits/92c732d66bea
[3/3] dm-ploop: fail writes to a read-only device
https://bitbucket.org/virtuozzocore/vzkernel.vzs/commits/7028a441789c
--
Konstantin Khorenko,
Virtuozzo Linux Kernel Team
_______________________________________________
Devel mailing list
[email protected]
https://lists.openvz.org/mailman/listinfo/devel
