Minio.sys big file?

Hey,

Recently, I have set up a backup system with duplicity
when it uploaded, I found it very long: more than 80gb for the pydio folder. But I don’t have more than 30gb of data. I searched why, and the /pydio/.minio.sys/tmp folder contains more than 50gb of data!
Can I empty it?
What is this folder ? I can’t find anything in the doc

Thanks!

Hello,

It could be the temp folder for uploading a file. Could you please try to upload a big file and monitor the process and the temp file in this folder?

Thanks for your answer. Can you tell me how I can monitor in just one folder ?

Hello,

I didn’t monitored the process but I monitored the file size inside the temp folder. When i upload a file, it creates new file.

Can I delete them ?

Has this ever been solved? I have the same problem. The .minio.sys/tmp grows up to 800GB when I start the resync of a datasource. The datasource itself is on disc and has only 85GB. The log has entries which show that s3://ip-of-cells-server/datasource is being analysed and finshes with S3 Walk Operation + Stats took {"d": "1h39m7.674269552s"}
Is there any way to turn of minio ?

Is there any way to turn of minio ?

If you want to be able to upload / download files, nope.

Yet, the tmp directory is used by minio for multipart transfer. When a transfer fails, parts are not deleted so that if you retry later, you already have some of the parts that were correctly uploaded.
So, if you have no pending transfer, you can empty this tmp subfolder.

Does that mean, if nobody is uploading into that data source (because that would be me), that somebody must be downloading data and that keeps failing? Is there any way to check if a transfer failed. There must be constantly failing transfers, because tmp is growing steadily.

I checked the tmp folder again and the only files in different sizes appear to be originated from a very large zip file (29GB). When such a file is growing, would that be an indication that somebody is downloading the large zip file? Or could that be caused by a resync as well?