jeroenvandenhoogen

Okay I double checked some of the hardlinks and I think it might be due to my checking them while the mover was running because the seem fine now. Still a little curious as to why the cache utilization wouldn't update during the move.

okay the mover just finished and utilization shot back to 17% (which makes sense). Still a little worried as to why it remained at 74% without updating util utilization once while it was actually running. Is this in any expected behaviour?

Hi all, I invoked the mover on my server about 3 hours ago and I just noticed that my cache utilization still had not gone down. The array was being written to and the logs did show the mover actually "moving" files. When I went to check hardlinks in the terminal with ls -li I noticed that for a lot of recently downloaded items hardlinks were not working either. Thanks in advance for your advice!

Thanks! This gives me some peace of mind. I will just let it finish building parity then.

Hi all, I am fairly new to using parity and I am building it for the first time. I would just like to know what to expect speed wise. When I started the parity sync last night it was running at the advertised 280mbs and now I wake up this morning and I see it running at 170mbs and now a little bit later it is in the 150mbs'. I paused the parity sync and did short SMART self-tests on all drives and they all (1x 18tb exos 18(parity drive), 2x 16tb exos 16) came back without errors. Temps have all been below 45c. Is this slowdown to be expected as the parity sync grows closer to completion? Could it be a disk fragmentation issue? If so would it be worth solving before completing the parity sync or should I wait for it to finish and solve it after? Thanks in advance! resolute-diagnostics-20250125-1056.zip