Can’t restore container backups, but VMs work

[DenverCM]

Hi all - I set up a new VE server. I backed up some containers and VMs to my Synology.

When I try restoring the backups the VMs work fine but the containers won’t restore - saying there isn’t enough space. One of my VMs is 100GB and it has no problem restoring.

I’m going from ZFS to LVM - could that be the problem?

Thanks!

 

[Johannes S]

I’m going from ZFS to LVM - could that be the problem?

In theory yes since zfs has compression and lvm not but I doubt that the impact is relevant in your case.

Can you please give the configuration of zfs and lvm plus the vm and container configs?

 

[DenverCM]

In theory yes since zfs has compression and lvm not but I doubt that the impact is relevant in your case.

Can you please give the configuration of zfs and lvm plus the vm and container configs?

Sorry - can I ask what details you’re looking for?

 

[Kingneutron]

Just to clarify, you should be restoring to lvm-thin for thin-provisioned disks and to support snapshots

 

[fiona]

Hi,

In theory yes since zfs has compression and lvm not but I doubt that the impact is relevant in your case.

yes, in some cases you'll need to specify a bigger disk size while restoring a container: https://forum.proxmox.com/threads/pct-restore-cannot-write-no-space-left-on-device.99481/post-429458

Can you please give the configuration of zfs and lvm plus the vm and container configs?

That would be /etc/pve/storage.cfg and using the Show configuration button in the UI when selecting the container backup.

 

[DenverCM]

Thanks!

The container config:

arch: amd64cores: 3features: nesting=1hostname: qBittorrent-Homermemory: 2048net0: name=eth0,bridge=vmbr0,firewall=1,gw=10.0.1.9,hwaddr=1A:0B:AE:28:FB:92,ip=10.0.1.233/24,ip6=dhcp,type=vethonboot: 1ostype: ubunturootfs: local-zfs:subvol-122-disk-1,size=8Gstartup: order=10,up=120swap: 2048unused0: local-zfs:subvol-122-disk-2


VM Config:

bootdisk: sata0cores: 4ide2: none,media=cdrommemory: 6144name: Win10-UniFinet0: e1000=4E:6B:36:27:63:6A,bridge=vmbr0numa: 0onboot: 1ostype: win10sata0: local-zfs:vm-103-disk-0,size=100Gscsihw: virtio-scsi-pcismbios1: uuid=f4f8afe7-2e9a-409f-b571-f002bcbcc323sockets: 1vga: memory=4#qmdump#map:sata0:drive-sata0:local-zfs::

 

[fiona]

arch: amd64cores: 3features: nesting=1hostname: qBittorrent-Homermemory: 2048net0: name=eth0,bridge=vmbr0,firewall=1,gw=10.0.1.9,hwaddr=1A:0B:AE:28:FB:92,ip=10.0.1.233/24,ip6=dhcp,type=vethonboot: 1ostype: ubunturootfs: local-zfs:subvol-122-disk-1,size=8Gstartup: order=10,up=120swap: 2048unused0: local-zfs:subvol-122-disk-2

Note for the future, you can use [CODE][/CODE] tags to have nicely formatted information.

Did you already try restoring while increasing the rootfs size (see link in previous post)?

 

[DenverCM]

Note for the future, you can use [CODE][/CODE] tags to have nicely formatted information.

Did you already try restoring while increasing the rootfs size (see link in previous post)?

Yes and got it working. Here's what I did:

Added a second SSD for ZFS then ran the command below.

zfs create -o mountpoint=/zfspool/subvol-101-disk-1 zfspool/subvol-101-disk-1

pct restore 101 /mnt/pve/SynologyBackups/dump/vzdump-lxc-122-2024_12_03-10_58_55.tar.zst --rootfs zfspool:subvol-101-disk-1,size=30G

The container was set up originally with an 8 GB size but it wanted 14 GB during the restore. Had to use Chat GPT to figure out the exact syntax (and for creating the mount point).

Thanks for all the help!

 

[fiona]

Yes and got it working. Here's what I did:

Added a second SSD for ZFS then ran the command below.

zfs create -o mountpoint=/zfspool/subvol-101-disk-1 zfspool/subvol-101-disk-1

pct restore 101 /mnt/pve/SynologyBackups/dump/vzdump-lxc-122-2024_12_03-10_58_55.tar.zst --rootfs zfspool:subvol-101-disk-1,size=30G

The container was set up originally with an 8 GB size but it wanted 14 GB during the restore. Had to use Chat GPT to figure out the exact syntax (and for creating the mount point).

Thanks for all the help!

There is no quota on the container's volume now, because you didn't specify anything when creating the ZFS dataset. The size option given later doesn't retroactively change that. To actually allocate a new volume during restore with a certain size/quota, for example 30 GB, you can use --rootfs zfspool:30. This syntax is already mentioned in the post linked earlier.

The dataset you created manually is also missing other options, Proxmox VE would set, see: https://git.proxmox.com/?p=pve-stor...2b62df7ebeda572cdf56ef19be872d56;hb=HEAD#l332

 

[DenverCM]

There is no quota on the container's volume now, because you didn't specify anything when creating the ZFS dataset. The size option given later doesn't retroactively change that. To actually allocate a new volume during restore with a certain size/quota, for example 30 GB, you can use --rootfs zfspool:30. This syntax is already mentioned in the post linked earlier.

The dataset you created manually is also missing other options, Proxmox VE would set, see: https://git.proxmox.com/?p=pve-stor...2b62df7ebeda572cdf56ef19be872d56;hb=HEAD#l332

Thanks! I ran this command to set the quota:

zfs set quota=30G zfspool/subvol-101-disk-1

That seems to be working. In the future, you're saying this would be easier/better?:

pct restore 101 /mnt/pve/SynologyBackups/dump/vzdump-lxc-122-2024_12_03-10_58_55.tar.zst --rootfs zfspool:30

And that's all I would have to do?

 

[fiona]

Thanks! I ran this command to set the quota:

zfs set quota=30G zfspool/subvol-101-disk-1

That seems to be working. In the future, you're saying this would be easier/better?:

pct restore 101 /mnt/pve/SynologyBackups/dump/vzdump-lxc-122-2024_12_03-10_58_55.tar.zst --rootfs zfspool:30

And that's all I would have to do?

Yes, that should do the trick.