-
From the error message, this looks like an issue encountered in the minio app itself. Please check if that instance has enough free space and also see if retrying the backup works and if it was only a temporary issue.
-
From the error message, this looks like an issue encountered in the minio app itself. Please check if that instance has enough free space and also see if retrying the backup works and if it was only a temporary issue.
-
From the error message, this looks like an issue encountered in the minio app itself. Please check if that instance has enough free space and also see if retrying the backup works and if it was only a temporary issue.
wrote on Mar 30, 2021, 10:44 AM last edited by@nebulon any clue on thath idk what it means sorry
minio log:
API: PutObjectPart(bucket=mybucket, object=myapp/snapshot/app_5b67e84d-40da-4604-80ec-45e8d610c839.tar.gz.enc)
Time: 00:20:11 UTC 03/30/2021
DeploymentID: d5aab97f-1878-40a6-a688-edf3b50b4960
RequestID: 1670F6C994C249CD
RemoteHost: 2.56.98.236
UserAgent: aws-sdk-nodejs/2.850.0 linux/v14.15.4 callback
Error: open /home/pi/data/.minio.sys/multipart/57fac6043320d82c0dc8e5332bbf92a93d28feab70e7de8bfaf6a3ea333d99aa/d279db31-dc24-4d74-959a-eb592d7915e0/fs.json: operation not permitted (*fs.PathError)
4: cmd/api-errors.go:2009:cmd.toAPIErrorCode()
3: cmd/api-errors.go:2034:cmd.toAPIError()
2: cmd/object-handlers.go:2272:cmd.objectAPIHandlers.PutObjectPartHandler()
1: net/http/server.go:2069:http.HandlerFunc.ServeHTTP() -
@nebulon any clue on thath idk what it means sorry
minio log:
API: PutObjectPart(bucket=mybucket, object=myapp/snapshot/app_5b67e84d-40da-4604-80ec-45e8d610c839.tar.gz.enc)
Time: 00:20:11 UTC 03/30/2021
DeploymentID: d5aab97f-1878-40a6-a688-edf3b50b4960
RequestID: 1670F6C994C249CD
RemoteHost: 2.56.98.236
UserAgent: aws-sdk-nodejs/2.850.0 linux/v14.15.4 callback
Error: open /home/pi/data/.minio.sys/multipart/57fac6043320d82c0dc8e5332bbf92a93d28feab70e7de8bfaf6a3ea333d99aa/d279db31-dc24-4d74-959a-eb592d7915e0/fs.json: operation not permitted (*fs.PathError)
4: cmd/api-errors.go:2009:cmd.toAPIErrorCode()
3: cmd/api-errors.go:2034:cmd.toAPIError()
2: cmd/object-handlers.go:2272:cmd.objectAPIHandlers.PutObjectPartHandler()
1: net/http/server.go:2069:http.HandlerFunc.ServeHTTP() -
@nebulon I got the newest version and it looks like the issues is by uploading multiple files with gives a 500 back.
Version:2021-03-26T00:00:41Z
Version: go1.16.2 | CPUs: 4@savity Are you running minio on the PI? (seems so from the path). Are you able to reproduce this issue when running minio on x86/some VPS? It seems to be something file system related with minio. Seems to me that some fs operation is not working with multipart uploads. Though it doesn't explain what the error is.
Maybe you can ask their issue tracker about it.
-
Trying to debug the backtrace a bit for fun:
https://github.com/minio/minio/blob/RELEASE.2021-03-26T00-00-41Z/cmd/object-handlers.go#L2272 seems to be last point of error. It seems somewhere in https://github.com/minio/minio/blob/7be71094710b966be624f10eeea25df02660493e/cmd/fs-v1-multipart.go#L369 failed
-
@savity Are you running minio on the PI? (seems so from the path). Are you able to reproduce this issue when running minio on x86/some VPS? It seems to be something file system related with minio. Seems to me that some fs operation is not working with multipart uploads. Though it doesn't explain what the error is.
Maybe you can ask their issue tracker about it.
-
Trying to debug the backtrace a bit for fun:
https://github.com/minio/minio/blob/RELEASE.2021-03-26T00-00-41Z/cmd/object-handlers.go#L2272 seems to be last point of error. It seems somewhere in https://github.com/minio/minio/blob/7be71094710b966be624f10eeea25df02660493e/cmd/fs-v1-multipart.go#L369 failed
wrote on Jul 22, 2021, 6:58 PM last edited by@girish said in Minio Backup not working:
Trying to debug the backtrace a bit for fun:
https://github.com/minio/minio/blob/RELEASE.2021-03-26T00-00-41Z/cmd/object-handlers.go#L2272 seems to be last point of error. It seems somewhere in https://github.com/minio/minio/blob/7be71094710b966be624f10eeea25df02660493e/cmd/fs-v1-multipart.go#L369 failedStill have it in the newest Minio Version and Cloudron Version
Vaultwarden Backup Works, but Nextcloud not
-
@girish said in Minio Backup not working:
Trying to debug the backtrace a bit for fun:
https://github.com/minio/minio/blob/RELEASE.2021-03-26T00-00-41Z/cmd/object-handlers.go#L2272 seems to be last point of error. It seems somewhere in https://github.com/minio/minio/blob/7be71094710b966be624f10eeea25df02660493e/cmd/fs-v1-multipart.go#L369 failedStill have it in the newest Minio Version and Cloudron Version
Vaultwarden Backup Works, but Nextcloud not
-
wrote on Jul 28, 2021, 1:07 PM last edited by
Could this be a memory constraint issue on the Pi?
-
wrote on Jul 29, 2021, 11:25 AM last edited by
Random thought but check permissions on the folder(/home/pi/data/.minio.sys/multipart/57fac6043320d82c0dc8e5332bbf92a93d28feab70e7de8bfaf6a3ea333d99aa/74f2a374-0090-44b8-8126-1f35d785abb7/), I ran into the same issue today.
Turned out to be permissions issue.
To verify run minio with sudo, this is a quick fix and should not be left like this.
In my scenario i was running minio on a mount was formatted as NTFS and hence i could not set permissions on the disk.
-
wrote on Jul 29, 2021, 3:31 PM last edited by
Perhaps there should be a permissions check script that puts warnings in the logs.
-
wrote on Aug 3, 2021, 6:45 PM last edited by
@robi @CraigGoodspeed To laate
After this here https://github.com/minio/minio/issues/12779 @girish
I decided to buy a synology make Raid change the Filesystem and do my backups on a Minio Docker.
Still don't get the answer thath it is the Harddrive why it was always possible making backups from "Vaultwarden" but not Nextcloud
