I have this setup for a storage container:
The sub-DS were set up as separate mountpoints for the LXC container, and that worked until recently. Today, however, I get this error when trying to start the container:
When trying to attach the mountpoint to the running container (started without any of the sub-DS):
The questions I now have:
Code:
# zfs list
NAME USED AVAIL REFER MOUNTPOINT
rpool 5.16T 5.61T 128K /rpool
rpool/ROOT 6.54G 5.61T 128K /rpool/ROOT
rpool/ROOT/pve-1 6.54G 5.61T 6.54G /
rpool/data 5.14T 5.61T 149K /rpool/data
[…]
rpool/data/subvol-112-disk-1 3.10T 5.61T 192K /rpool/data/subvol-112-disk-1
rpool/data/subvol-112-disk-1/data 96.4G 53.6G 96.4G /rpool/data/subvol-112-disk-1/data
rpool/data/subvol-112-disk-1/docker 24.7G 7.29G 24.7G /rpool/data/subvol-112-disk-1/docker
rpool/data/subvol-112-disk-1/games 136G 120G 136G /rpool/data/subvol-112-disk-1/games
[…]
The sub-DS were set up as separate mountpoints for the LXC container, and that worked until recently. Today, however, I get this error when trying to start the container:
unable to parse zfs volume name 'subvol-112-disk-1/data' (500)

When trying to attach the mountpoint to the running container (started without any of the sub-DS):
Parameter verification failed. (400)
mp1: unable to hotplug mp1: unable to parse zfs volume name 'subvol-112-disk-1/data'

pvedaemon log is limited to this
Code:
Nov 18 08:17:03 pmx pvedaemon[43495]: Could not rescan volume size - unable to parse zfs volume name 'subvol-112-disk-1/data'
Nov 18 08:18:42 pmx pvedaemon[43495]: Could not rescan volume size - unable to parse zfs volume name 'subvol-112-disk-1/data'
The questions I now have:
- When & why was this changed?
- Any way to get back the old behaviour?
