kavinci

I had a feeling it was something like this. I think it has to do with the pool configuration. I am running a waterfall across all drives and I think the management and reporting mechanism that might be the issue. I tried setting it but there must be something going on under the hood. The error I got kinda acts like there is but isn't enough space on the drive for larger files. It must be a side effect of this. What is CheeseMarathon's pool configuration?

I did not find a solution yet. I did however spin up Minio on my windows machine using Docker Desktop and WSL engine. That instance worked without any issues. That instance also didn't have any errors in the logs. My current assumption is that it is either the CheeseMarathon version or something to do with Unraid itself. I should also note that I got the CM version to work one time and one time only. The data config was pointed to the appdata location minio was installed to in unraid. This lead me to think that the container does not have sufficient privilege for the location I want so I tried giving creds to the root user in that directory which didn't work. Based on the error codes it almost acts like there is not enough space for the file which is where the share config comes in. It might be reporting to the container the drive space and importing based on that report. I run a waterfall setup and share space across drives for most shares. I tried changing the config for the share I wanted to use and that didn't work either.

No, I am hitting it directly from the IP of the unraid server.

I am running into an issue with Minio and not sure how to resolve it. I am unable to upload more than a few hundred KB files. So far the largest successful file was 112KB. Anything bigger keeps failing. I think it has something to do with these errors that keeps repeating in the logs API: SYSTEM Time: Sat Jun 04 2022 02:22:17 GMT-0700 (Pacific Daylight Time) DeploymentID: 3fc1b408-8f2b-462c-87fe-d859dda27ccd RequestID: RemoteHost: UserAgent: Error: Storage resources are insufficient for the write operation .minio.sys/buckets/.usage-cache.bin (cmd.InsufficientWriteQuorum) Backtrace: 0: internal/logger/logger.go:278:logger.LogIf() 1: cmd/erasure-single-drive.go:3076:cmd.(*erasureSingle).nsScanner.func1() API: SYSTEM Time: Sat Jun 04 2022 02:25:18 GMT-0700 (Pacific Daylight Time) DeploymentID: 3fc1b408-8f2b-462c-87fe-d859dda27ccd RequestID: RemoteHost: UserAgent: Error: srcVolume: .minio.sys/tmp, srcPath: 52346e68-2ad4-4da9-bc05-534b035c485e, dstVolume: .minio.sys/buckets:, dstPath: public/.usage-cache.bin - error file not found (*errors.errorString) Backtrace: 0: internal/logger/logger.go:278:logger.LogIf() 1: cmd/xl-storage.go:2071:cmd.(*xlStorage).RenameData.func1() 2: cmd/xl-storage.go:2331:cmd.(*xlStorage).RenameData() 3: cmd/xl-storage-disk-id-check.go:356:cmd.(*xlStorageDiskIDCheck).RenameData() 4: cmd/erasure-object.go:707:cmd.renameData.func1() 5: internal/sync/errgroup/errgroup.go:123:errgroup.(*Group).Go.func1() I have tried looking at permissions for the share and rebuilding the container a few times with no luck. My /data is pointed to /mnt/user/object_storage/ which is a just a share I created, nothing special. Anyone know how to fix this?