Weed Filer backup errors in the log
113 views
Skip to first unread message
venkata Kolla
Apr 22, 2022, 6:27:07 AM4/22/22
to Seaweed File System
I started a weed filer.backup process to backup all the data to an S3
bucket. Lot of logs are getting generated with the below error messages.
Do i need to update any config to resolve or these messages can be
ignored?
s3_write.go:99] [persistent-backup] completeMultipartUpload buckets/persistent/BEV_Processed_Data/2011_09_30/2011_09_30/GT_BEV_Output/0000000168.png: EntityTooSmall: Your proposed upload is smaller than the minimum allowed size
Apr 21 09:20:14 worker-server-004 seaweedfs-filer-backup[3076983]: #011status code: 400, request id: 10N2S6X73QVWK78G, host id: y2dsSnf7YTtMLIQSCW1eqrgvkom3lQ5HZegDjL4MgU8KkjDG/4U83BOr6qdUtHm8S4ScxI5HwZw=
Another error
malformed xml the xml you provided was not well formed or did not validate against
venkata Kolla
Apr 26, 2022, 5:23:06 AM4/26/22
to Seaweed File System
This issue happens with empty files or files with small content. Looks
like aws s3 multipart upload does not accept streaming empty files. Is
there any setting on SeaweedFs that i am missing?
Reply all
Reply to author
Forward
0 new messages