CT Snapshot not working

digidax

Renowned Member
Mar 23, 2009
100
1
83
Hi there,
have updated node from 7 to 8.3.2

On one node with one CT, there is snapshot not possible.
Initial, the cube followed by NOW is missing too:
1736332183899.png
When doing a snapshot, the task is done but not displayed in list.
Doing the snapshot again "TASK ERROR: snapshot name 'test' already used" comes up.
So where are the snapshots? Seems that they are done?

Code:
:~# cat /etc/pve/lxc/211.conf
#CentOS 8
arch: amd64
cores: 8
dev0: /dev/sda1,mode=0777
hostname: bareos.local
memory: 7392
net0: name=eth0,bridge=vmbr0,gw=192.168.130.254,hwaddr=CA:DA:92:A4:FA:5D,ip=192.168.130.211/24,type=veth
net1: name=eth1,bridge=vmbr1,hwaddr=62:AF:AE:42:11:A0,ip=192.168.110.211/24,type=veth
onboot: 1
ostype: centos
parent: test
rootfs: pve_zfs:subvol-211-disk-0,size=300G
swap: 4096
lxc.cgroup2.devices.allow: c 9:* rwm
lxc.mount.entry: /dev/st0 /dev/st0 none bind,optional,create=dir
lxc.mount.entry: /dev/nst0 /dev/nst0 none bind,optional,create=dir

[pre_update]
arch: amd64
cores: 8
dev0: /dev/sda1,mode=0777
hostname: bareos.celebraterecords.com
memory: 7392
net0: name=eth0,bridge=vmbr0,gw=192.168.130.254,hwaddr=CA:DA:92:A4:FA:5D,ip=192.168.130.211/24,type=veth
net1: name=eth1,bridge=vmbr1,hwaddr=62:AF:AE:42:11:A0,ip=192.168.110.211/24,type=veth
onboot: 1
ostype: centos
parent: vzdump
rootfs: pve_zfs:subvol-211-disk-0,size=300G
snaptime: 1736331136
swap: 4096
lxc.cgroup2.devices.allow: c 9:* rwm
lxc.mount.entry: /dev/st0 /dev/st0 none bind,optional,create=dir
lxc.mount.entry: /dev/nst0 /dev/nst0 none bind,optional,create=dir

[test]
arch: amd64
cores: 8
dev0: /dev/sda1,mode=0777
hostname: bareos.celebraterecords.com
memory: 7392
net0: name=eth0,bridge=vmbr0,gw=192.168.130.254,hwaddr=CA:DA:92:A4:FA:5D,ip=192.168.130.211/24,type=veth
net1: name=eth1,bridge=vmbr1,hwaddr=62:AF:AE:42:11:A0,ip=192.168.110.211/24,type=veth
onboot: 1
ostype: centos
parent: pre_update
rootfs: pve_zfs:subvol-211-disk-0,size=300G
snaptime: 1736331604
swap: 4096
lxc.cgroup2.devices.allow: c 9:* rwm
lxc.mount.entry: /dev/st0 /dev/st0 none bind,optional,create=dir
lxc.mount.entry: /dev/nst0 /dev/nst0 none bind,optional,create=dir

[vzdump]
#vzdump backup snapshot
arch: amd64
cores: 8
dev0: /dev/sda1,mode=0777
hostname: bareos.celebraterecords.com
memory: 7392
net0: name=eth0,bridge=vmbr0,gw=192.168.130.254,hwaddr=CA:DA:92:A4:FA:5D,ip=192.168.130.211/24,type=veth
net1: name=eth1,bridge=vmbr1,hwaddr=62:AF:AE:42:11:A0,ip=192.168.110.211/24,type=veth
onboot: 1
ostype: centos
parent: vzdump
rootfs: pve_zfs:subvol-211-disk-0,size=300G
snaptime: 1736316223
swap: 4096
lxc.cgroup2.devices.allow: c 9:* rwm
lxc.mount.entry: /dev/st0 /dev/st0 none bind,optional,create=dir
lxc.mount.entry: /dev/nst0 /dev/nst0 none bind,optional,create=dir

It seems, that the base config uses the parameter "parent: test" as linking to an other snapshot but there is no snaptime, so it makes no sense.
Can I delete the "parent" entry in the first section and also the [test], [vzdump] and [pre_update] blocks? If yes, are there any allocated disk spaces I have to delete too?

Thank, Frank
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!