That's pretty much it, i.e. VLAN devices (ethX.1234) take 5 additional characters for instance. 8 was chosen so there's still some wiggle room for autogenerated names for network devices.
thanks!
Most likely the Web UI showed a state `running` state for the VM 109 because corosync or cluster were in no quorum and status updates from pvestatd couldn't propagate.
Hard to know/confirm without syslog.
The main issue that happens here is if the backup target (storage, network, ...) is not fast enough to ACK a write. As the backup will halt the write operation of the VM until it got the ACK that this part of the VM disk in question has been...