[GH-ISSUE #191] Large storage sizes supporting #51

Open
opened 2026-03-03 15:29:53 +03:00 by kerem · 1 comment
Owner

Originally created by @p-drift on GitHub (Apr 22, 2025).
Original GitHub issue: https://github.com/luthermonson/go-proxmox/issues/191

Hello!

On one of the nodes in my PVE cluster, there is a Directory-type storage which is a mount point for an S3 bucket via MinIO. The fuse.geesefs driver doesn't support detecting the bucket size, so it reports it as 1.13 PB:

sudo pvesh get /nodes/$(hostname)/storage --noborder --human-readable 0
content   storage        type active avail           enabled shared total           used used_fraction
backup    minio_backup   dir  1      1125899906842624 1       0      1125899906842624 0    0

When calling func (*Node) Storages for this node, I get the following error:

json: cannot unmarshal number 1.12589990684262e+15 into Go struct field Storage.Total of type uint64

Is there any plan to support such large storage sizes in the future?

Originally created by @p-drift on GitHub (Apr 22, 2025). Original GitHub issue: https://github.com/luthermonson/go-proxmox/issues/191 Hello! On one of the nodes in my PVE cluster, there is a Directory-type storage which is a mount point for an S3 bucket via MinIO. The fuse.geesefs driver doesn't support detecting the bucket size, so it reports it as 1.13 PB: ```bash sudo pvesh get /nodes/$(hostname)/storage --noborder --human-readable 0 content storage type active avail enabled shared total used used_fraction backup minio_backup dir 1 1125899906842624 1 0 1125899906842624 0 0 ``` When calling `func (*Node) Storages` for this node, I get the following error: ```go json: cannot unmarshal number 1.12589990684262e+15 into Go struct field Storage.Total of type uint64 ```` Is there any plan to support such large storage sizes in the future?
Author
Owner

@luthermonson commented on GitHub (Apr 22, 2025):

the fix is probably to migrate to a big.Int

<!-- gh-comment-id:2821697885 --> @luthermonson commented on GitHub (Apr 22, 2025): the fix is probably to migrate to a big.Int
Sign in to join this conversation.
No labels
pull-request
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/go-proxmox#51
No description provided.