mirror of
https://github.com/Corsinvest/cv4pve-autosnap.git
synced 2026-04-26 01:15:48 +03:00
[GH-ISSUE #51] Skip snapshot when disk going full #47
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/cv4pve-autosnap#47
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @bds-congnguyen on GitHub (Jul 26, 2021).
Original GitHub issue: https://github.com/Corsinvest/cv4pve-autosnap/issues/51
Hi there,
Thank for awesome tool, but in proxmox when a disk got full, all QMEMU/LXC instance will get Pause due to I/O error so to avoid when snapshot cause disk getting full, can we have a feature like skip snapshot when disk is over 95% capacity?
@franklupo commented on GitHub (Aug 23, 2021):
Hi,
All disks attached to the virtual machine should be checked. Now I think how this functionality can be implemented.
best regards
@franklupo commented on GitHub (Dec 3, 2021):
Hi,
I want to add a parameter --max-perc-storage to specify any percentage for statrage other than the default 95%.
For each VM I check the disks on which storage it is supported, from the storage I check used if lower percentage. If one of the disks is on a storage out of range, the snapshot of the VM will not be taken and an error will be reported.
What do you think?
best regards
@adrianvg commented on GitHub (Dec 4, 2021):
@franklupo
Is this the error you mention will be reported?
This autosnap is being run on a proxmox cluster node that is 90% full.
@bds-congnguyen commented on GitHub (Dec 4, 2021):
yes, I've tried with storage usage is 91,5% and --max-perc-storage=90 and return same error
@franklupo commented on GitHub (Dec 4, 2021):
Hi,
Which version do you use of Proxmox?
@franklupo commented on GitHub (Dec 4, 2021):
No, this is an error. Can execute with --debug optional attach log.
Remember remove password
Best regards
@adrianvg commented on GitHub (Dec 5, 2021):
@franklupo
Attached. Thanks for any insights!
autosnap.log
@franklupo commented on GitHub (Dec 5, 2021):
The error is fixed in new version.
Please download last release.
Best rrgards
@adrianvg commented on GitHub (Dec 5, 2021):
Just noticed it.
Trying it out. Seems okay so far.
Thanks for the quick fix!
Update:
It's done. No problems. Thank you very much!
@bds-congnguyen commented on GitHub (Dec 6, 2021):
Hi there and @franklupo
I think the table of Storage status is not right, since I'm running snapshot only for pve5 but table also show storages of other hosts
also, we should skip check storage if this type of storage is not contains
disk images,containerlikepbs_ohan_backupas below because it's storage of proxmox backup server and contain only VZDump backup file@franklupo commented on GitHub (Dec 6, 2021):
Ok, in the next release i check the content type of storage and the nodes used for Autosnap.
Best regards