3 posts were split to a new topic: Piecemigrate:chore couldn’t migrate {“error”: "duplicate pieces differ: headers don’t match
If you wonder about migration speed, here it is:
Synology NAS 216+ 8GB RAM, 2 nodes on 2 IronWolf 8TB.
Node 2 no migration and badger active.
Node 1 migration active and badger on: 10000 pieces/ 12min processed.
I don’t know if the hardware (CPU/RAM) has a noticeable influence. I will see with the next migration on a more powerful machine.
To put into perspective, my biggest node has 11.15TB data, 53798100 pieces; so the migration should take 45 days.
1 Like
where do you see the migration progress ? i started the migration yesterday evening but the only progress i am seeing is the increasing number of files in the hashstore directory, but nothing in the logs. in 12 hours it went up by ~ 200 GB. So my 8 TB node would take like 20 days (on a 4-core E3 v6 Xeon CPU)
In logs, info level, with some custom filtering. Search my post in “log custom level” thread.
The startup piece scan gives you the no. of pieces on each sat and the migration chore gives you a log entry after each 10.000 pieces processed. I can’t post the specific entries right now, but they are obvious.
thanks i see. mine looks like 10.000 pieces/7 minutes. i dont see the no. of pieces in the logs, but my storj folder contains 35 Million files. If 1 piece = 1 file it will be around 17 days for the migration.