I want to remove my 3 smallest disks so I'm moving files from them onto the other disks in the array. The first 2 disks moved files at 18MB/s, slow but they didn't have too much on them. My third disk only has 3TB on it, but it's moving files at 2-4MB/s.

 

To move the files I used the browse mnt option, next to the drive, on the Main page. I tried using Midnight Commander, but it was the same speeds.

 

Is there something wrong and is there a way to speed this up?

apollo-diagnostics-20221222-0913.zip

Diags show writes to disk5 at about 30MB/s, which is about right for disk to disk copy.

19 minutes ago, JorgeB said:

Diags show writes to disk5 at about 30MB/s, which is about right for disk to disk copy.

Does it show multiple data points or is it just a snapshot? I'm wondering if that's a spike. Unless the UI is not displaying the correct speeds, it's a sustained 2MB/s~. I left it going nearly 24 hours and it managed less than 200GB.

Edited December 22, 20223 yr by Benji

Post new diags to see.

I had to reboot for something and the speeds seem to have returned to normal. I'll keep an eye on it and post back if the speeds drop over time.

 

Thanks for your replies and help.

The main page and the move window when browsing the disc show different speeds. The main page shows the disk at 31.5MB/s, at the exact same time the Move window is showing 8MB/s. I'm transferring from Disk 2 to 5. I turned on reconstruct write and that did improve speeds on main page, but not on move page.

 

 

Which is correct?

apollo-diagnostics-20221222-2220.zip

Edited December 22, 20223 yr by Benji

What are all of those reads on disk1 about???

10 hours ago, Frank1940 said:

What are all of those reads on disk1 about???

 

I mentioned in the post I had enabled reconstruct write to speed up the process. It doubles the write speed of the array by writing data immediately, but it requires all other disks to be read simultaneously for pairity.

 

I don't keep it on as a rule, but for large transfers it's a real time saver.

Edited December 23, 20223 yr by Benji

GUI should show the correct stats, and they match what I've seen on the diags.

I don't think it is displaying the correct speed. Since that screenshot, 36 hours ago, it's only moved 700GB. It's gone from 22% to 55% complete.

 

That definitely points towards the Move window being the correct estimate.

apollo-diagnostics-20221224-1038.zip

Edited December 24, 20223 yr by Benji

Are you sure no other operation is going on? Diags still show similar speeds, stop that move operation, wait a couple of minutes and post new diags.

Nothing that I can see.

 

I stopped the transfer, waited a few mins, but the disk activity hasn't stopped. I checked htop and I can see rsync is still running from disk2 > disk5. Does it still finish the current transfer after stopping it?

apollo-diagnostics-20221224-1306.zip

OT about the slow buy i think its a great tip:

 

Benji, i think the best to move files from "pool" to specify disk is setting up a new share, and mark this share to use only the disk you want to use for this files, after you can safely move from actual share to the new share that ill store the files into just one disk, after move you can remove the setting of fixed disk on this share.

 

I always do this when i need to fix files from disks pool to just specify disk in the pool

Edited December 24, 20223 yr by Ronan C

On 12/24/2022 at 1:08 PM, Benji said:

checked htop and I can see rsync is still running from disk2 > disk5. Does it still finish the current transfer after stopping it?

No sure, you could also have multiple transfers going on, try killing the rsync process(es).

It was doing many multiple transfers at the same time and not completing any of them. It seems whenever I start a file move from that part, it just breaks and even stopping the process won't stop rsync. You do have to kill them.

 

Anyway, I tried midnight commander again. I realise the last time I tried it was after the other method, which meant the transfers would have still been going on in the background. Anyway, on a fresh attempt MC transferred the remaining 2TB overnight with no issue.

 

So either there's something wrong with my setup when attempting moves from the browse disk function or it's a bug. Either way, avoiding it and using MC was the solution.