mirror of
https://github.com/Corsinvest/cv4pve-autosnap.git
synced 2026-04-25 08:55:49 +03:00
[GH-ISSUE #93] Storage size issue #85
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/cv4pve-autosnap#85
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 @sparkerb on GitHub (Oct 18, 2024).
Original GitHub issue: https://github.com/Corsinvest/cv4pve-autosnap/issues/93
What happened?
The tool seems to be failing over one of storage medium, looking at your cluster the culprit seems to be our S3FS disk that automatically gets mounted to each node and provides templates which the customer can use to easily deploy VM's.
This S3FS disk reports itself as 16 EiB (16 Exbibytes) which the tools seem to crash upon. Seen that more S3 mounts can report such huges size like these, the problems seems to exist in the tool itself.
Expected behavior
Accept large storage.
Relevant log output
Proxmox VE Version
8.2.7
Version (bug)
Latest
Version (working)
Latest
On what operating system are you experiencing the issue?
Linux
Pull Request
@franklupo commented on GitHub (Dec 9, 2024):
in the next version it will be fixed