[GH-ISSUE #93] Storage size issue #85

Closed
opened 2026-02-26 17:44:20 +03:00 by kerem · 1 comment
Owner

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

Unhandled exception: Newtonsoft.Json.JsonSerializationException: Error converting value 18446744073692774400 to type 'System.Int64'. Path '[8].maxdisk', line 1, position 1808. ---> System.InvalidOperationException: Can not convert from BigInteger to System.Int64. ---> System.OverflowException: Value was either too large or too small for an Int64. at System.Numerics.BigInteger.op_Explicit(BigInteger value) at Newtonsoft.Json.Utilities.ConvertUtils.FromBigInteger(BigInteger i, Type targetType) --- End of inner exception stack trace --- at Newtonsoft.Json.Utilities.ConvertUtils.FromBigInteger(BigInteger i, Type targetType) at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.EnsureType(JsonReader reader, Object value, CultureInfo culture, JsonContract contract, Type targetType) --- End of inner exception stack trace ---

Proxmox VE Version

8.2.7

Version (bug)

Latest

Version (working)

Latest

On what operating system are you experiencing the issue?

Linux

Pull Request

  • I would like to do a Pull Request
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 ```shell Unhandled exception: Newtonsoft.Json.JsonSerializationException: Error converting value 18446744073692774400 to type 'System.Int64'. Path '[8].maxdisk', line 1, position 1808. ---> System.InvalidOperationException: Can not convert from BigInteger to System.Int64. ---> System.OverflowException: Value was either too large or too small for an Int64. at System.Numerics.BigInteger.op_Explicit(BigInteger value) at Newtonsoft.Json.Utilities.ConvertUtils.FromBigInteger(BigInteger i, Type targetType) --- End of inner exception stack trace --- at Newtonsoft.Json.Utilities.ConvertUtils.FromBigInteger(BigInteger i, Type targetType) at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.EnsureType(JsonReader reader, Object value, CultureInfo culture, JsonContract contract, Type targetType) --- End of inner exception stack trace --- ``` ### Proxmox VE Version 8.2.7 ### Version (bug) Latest ### Version (working) Latest ### On what operating system are you experiencing the issue? Linux ### Pull Request - [X] I would like to do a Pull Request
kerem 2026-02-26 17:44:20 +03:00
Author
Owner

@franklupo commented on GitHub (Dec 9, 2024):

in the next version it will be fixed

<!-- gh-comment-id:2528013410 --> @franklupo commented on GitHub (Dec 9, 2024): in the next version it will be fixed
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/cv4pve-autosnap#85
No description provided.