Closed Nopsty closed 5 years ago
Fixed the read of existing snapshot names in:
This fixes: *) status output
Before on Ceph: eve4pve-autosnap status VM SNAPSHOTS LABEL 100 190620230005-daily- ::
After: eve4pve-autosnap status VM SNAPSHOTS LABEL 100 190627160350 daily
testet with: zfs, ceph, local
*) correct auto delete of snapshots on ZFS. (Before snapshots on some ZFS hosts were not deleted)
Output from ZFS on pve host 1: pve1# qm listsnapshot 310 -> autodaily190623230006 2019-06-23 23:00:13 eve4pve-autosnap -> autodaily190624230004 2019-06-24 23:00:11 eve4pve-autosnap `-> autodaily190625230017 2019-06-25 23:01:10 eve4pve-autosnap
-> autodaily190623230006 2019-06-23 23:00:13 eve4pve-autosnap
Output from ZFS on pve host 2: pve2# qm listsnapshot 1902 autodaily190627160118 no-parent eve4pve-autosnap autodaily190627174021 autodaily190627173751 eve4pve-autosnap autodaily190627173751 autodaily190627160118 eve4pve-autosnap
(Standard pve installations, both full updated)
Fixed the read of existing snapshot names in:
This fixes: *) status output
Before on Ceph: eve4pve-autosnap status VM SNAPSHOTS LABEL 100 190620230005-daily- ::
After: eve4pve-autosnap status VM SNAPSHOTS LABEL 100 190627160350 daily
testet with: zfs, ceph, local
*) correct auto delete of snapshots on ZFS. (Before snapshots on some ZFS hosts were not deleted)
Output from ZFS on pve host 1: pve1# qm listsnapshot 310
-> autodaily190623230006 2019-06-23 23:00:13 eve4pve-autosnap
-> autodaily190624230004 2019-06-24 23:00:11 eve4pve-autosnap `-> autodaily190625230017 2019-06-25 23:01:10 eve4pve-autosnapOutput from ZFS on pve host 2: pve2# qm listsnapshot 1902 autodaily190627160118 no-parent eve4pve-autosnap autodaily190627174021 autodaily190627173751 eve4pve-autosnap autodaily190627173751 autodaily190627160118 eve4pve-autosnap
(Standard pve installations, both full updated)