Unsure whether LUKS on LVM is being handled correctly

[ppp7032]

My system consists of a single LVM VG (named vg) with a single LV (cryptroot). On this LV is LUKS with a BTRFS filesystem on top of that. Setting this up to boot correctly was quite annoying as no amount of linux kernel arguments I could find would help, until I tried "rd.auto=1".

Anyway, I noticed a strange message when shutting down:

As you can see, it looks like runit is trying and failing to deactivate the LVM VG (presumably because it doesn't take into consideration there may be a LUKS volume on top of it. LVM on LUKS is definitely a more common setup, after all.

A) Is runit really forcefully deactiving my VG with the LUKS volume still open on top of it?
B) Does this carry a risk of data corruption?

Here's the messages seen on boot for reference:

[Duncaen]

I think this would happen even with just one LUKS or LVM alone if its the root filesystem because it can't be unmounted while its being used during the shutdown sequence. Instead the rootfs is remounted read only to avoid data loss.

The only way to deactivate the rootfs devices would be to switch back into the initramfs on shutdown.

Don't think anyone reported actual issues because of it though.

Other init scripts, like gentoos openrc scripts have the same issue. I think the only init system that fully implements switching back into the initramfs on shutdown is systemd.