Search found 18 matches
- 27 Mar 2024, 18:10
- Forum: System Update
- Topic: Problem with TOS 6 and system partition smaller than 8Gbyte
- Replies: 0
- Views: 497
Problem with TOS 6 and system partition smaller than 8Gbyte
Hello. I had an issue trying to update TOS from last 5.x to 6.0beta, because system partition was too small (I had 2.9Gb, but 8Gbyte system partition is required). I want to explain how I solved (now I am running 6 beta) without any data loss: My system partition was only 2.6Gbyte; using ssh, i chec...
- 25 Jan 2024, 21:33
- Forum: CloudSync
- Topic: Cloudsync / S3 and temporary files with versioning
- Replies: 5
- Views: 611
Re: Cloudsync / S3 and temporary files with versioning
I can confirm that whith today's upgrade all is working as expected. No temporary files, and no problem with >50Gb size files.
Thank you again.
Thank you again.
- 16 Jan 2024, 18:50
- Forum: CloudSync
- Topic: Cloudsync / S3 and temporary files with versioning
- Replies: 5
- Views: 611
Re: Cloudsync / S3 and temporary files with versioning
Thank you very much.
PS: as I can see, s3 will show the uploaded files only after a complete upload
I will wait for the new version so I can save my datas.
PS: as I can see, s3 will show the uploaded files only after a complete upload
I will wait for the new version so I can save my datas.
- 16 Jan 2024, 16:33
- Forum: CloudSync
- Topic: Cloudsync / S3 and temporary files with versioning
- Replies: 5
- Views: 611
Re: Cloudsync / S3 and temporary files with versioning
This is what happens... this log is of my ceph S3 cluster, so "server side". Fist, file is uploaded normally (with rclone) and his name is the temporary file: 212.66.111.241 - - [16/Jan/2024:09:15:48 +0100] "PUT /terramaster-fabry/Foto/2019/2019-08-17-BoscoDelleFavole/ActionCam/DCIM/1...
- 16 Jan 2024, 16:10
- Forum: CloudSync
- Topic: Cloudsync / S3 and temporary files with versioning
- Replies: 5
- Views: 611
Re: Cloudsync / S3 and temporary files with versioning
The problema with "rename" is with size of about 3.5Gbyte or more.
- 15 Jan 2024, 16:30
- Forum: CloudSync
- Topic: Cloudsync / S3 and temporary files with versioning
- Replies: 5
- Views: 611
Cloudsync / S3 and temporary files with versioning
Hello. I am using cloudsync to backup my nas to a s3 bucket (with some small modification on config file and sqlite3 database, I can change from Amazon to Ceph s3 endpoint). I have two problems: cloudsyncd uploads all the files with a temporary filename (.cloudsyncd_downloading_ORIGINALFILENAME), af...
- 09 Jan 2024, 16:43
- Forum: CloudSync
- Topic: cloudsync s3 and 100.000 files
- Replies: 4
- Views: 783
Re: cloudsync s3 and 100.000 files
Of course, I am available, also now if you want.
- 08 Jan 2024, 16:23
- Forum: CloudSync
- Topic: cloudsync s3 and 100.000 files
- Replies: 4
- Views: 783
Re: cloudsync s3 and 100.000 files
Hello.
There are news regarding this bug fix ?
I was waiting for an update that fix, because now I can't backup my nas.
Thank you.
There are news regarding this bug fix ?
I was waiting for an update that fix, because now I can't backup my nas.
Thank you.
- 18 Dec 2023, 16:15
- Forum: CloudSync
- Topic: cloudsync s3 and 100.000 files
- Replies: 4
- Views: 783
cloudsync s3 and 100.000 files
Hello.
With last release (TOS and cloudsync), I have folders with more than 100.000 files, but cloudsync stop syncing after 100.002 files.
No any info from logfile, and activity tells that is still syncing (100.002 files).
Same issue with two different nas and different file structure.
With last release (TOS and cloudsync), I have folders with more than 100.000 files, but cloudsync stop syncing after 100.002 files.
No any info from logfile, and activity tells that is still syncing (100.002 files).
Same issue with two different nas and different file structure.
- 15 Dec 2023, 19:45
- Forum: CloudSync
- Topic: AmazonS3 and 3.0.15 not working
- Replies: 7
- Views: 843
Re: AmazonS3 and 3.0.15 not working
Solved with remote support.
It was due to a "/" character on my secret key.
With a new secret key it can work without any problem.
It was due to a "/" character on my secret key.
With a new secret key it can work without any problem.