Maximum useable space limited by Volume Size Limit and Volume Count

[max]

Hi Forum,

I can't seem to get Seaweed to use my available disk space or more than one bucket. Has anyone had the same issue?

Background: I have been looking to replace my Minio S3 service with either garage SeaweedFS or RustFS and choose Seaweed. My main use case is to use S3 for tarball backups and I have a server with 14TB of space to use for this. Minio was good for this, however it no longer has a future in the OS community. SeeweedFS works well and is good to use, plus it is stable. RustFS also works well, has fewer features (that I probably don't use) but is not stable yet.

Issues: After installing Seaweed it works fine as installed, but it appears to be set to a maximum useable limit of 8Gb and also I get errors if I try to use any second bucket at all - no free volumes. I see in file manager and the Seaweed dash that I already have 8 volumes. The my first Cloudron Server backup saves fine, but fail after 8 Gb, my second Cloudron server fails if I try to set it to a different bucket with the no free volumes error in the logs.

Using weed volume.list I can see the volume size limit is set to 1024 MB (also visible in the dashboard) and the max number of volumes is set to 8. I have not been able to increase these and it appears that the Cloudron App has set some parameters in the start script which I haven't found a way of overriding in env.sh.

I suspect I need to override the defaults to expand the usable space, for example I could do 430 volumes × 30,000 MB = 12,900,000 MB => 12,900,000 MB = 12.30 TB of raw data storage, leaving headroom for indexes etc, but I can't seem to override these in the Cloudron App:

• volumeSizeLimitMB - I understand there is a build limit to 30Gb (30000) to do with 4 bit sizes

• maxVolumeCounts - either to 0 for auto or a sufficiently large number that x the Size uses the available disk space

I have tried numerous options in env.sh and none change the setting, even if I remove the existing files, volumes and collections. Options include:
export WEED_VOLUME_ARGS="-max=126" or export WEED_MASTER_ARGS="-volumeSizeLimitMB=30000 -maxVolumeCounts=hdd:126"

I can achieve this with a custom start script called from env.sh (which shows it is being run), but of course this breaks everything Cloudron. Is there a way to do this, or am I missing something?

If not, can you expose the variables so that we can achieve using the available disk space and multiple buckets (collections)?

Thanks in advance!!!