I've had a similar problem. It was worse because i had to unmount everything up to the root.
I think I set the datasets for machines to automount by setting a mountpoint attribute that was missing before. I can't recall if that was it though. Do you have it set? zfs get mountpoint /rbd/... Best, Daniel On 9/12/2019 2:18 AM, Mike O'Connor wrote: > HI All > > I just finished upgrading from V5 to V6 of Proxmox and have an issue > with LXC 's not starting. > > The issue seems to be that the LXC is being started with out first > mounting the ZFS subvolume. > This results in a dev directory being created which then means ZFS will > not mount over anymore because there are files in the mount point > > Mount does not work > Code: > > root@pve:/rbd# zfs mount rbd/subvol-109-disk-0 > cannot mount '/rbd/subvol-109-disk-0': directory is not empty > > There is a directory created by the attempt to start the lXC > Code: > > root@pve:/rbd# find /rbd/subvol-109*/ > /rbd/subvol-109-disk-0/ > /rbd/subvol-109-disk-0/dev > > Remove the directory > Code: > > rm -rf /rbd/subvol-109-disk-0/dev/ > > Mount the rbd volume > Code: > > root@pve:/rbd# zfs mount rbd/subvol-109-disk-0 > > I can then start the LXC from the web page or via the cli. > > Question: > What mounts the zfs subvol ? > Is this a ZFS issue of not mounting the subvol at boot ? > Should Proxmox be mounting the image ? > Should Proxmox not be checking its mounted before starting the LXC ? > > I've been able to start the LXC but after a reboot, it seems I have to > manual fix the mounts again. > > Thanks > > _______________________________________________ > pve-user mailing list > pve-user@pve.proxmox.com > https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user _______________________________________________ pve-user mailing list pve-user@pve.proxmox.com https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user