@jihiggs Re
Given you are now on 4.5.9-1 you could consider moving to a mixed raid profile:
BUT ONLY IF YOU ARE ALREADY ON A “BUILT ON openSUSE” LEAP 15.4 BASE.
Or Tumbleweed of course.
But if you are still on a Leap 15.3 base then take a look at our in-place update HowTo:
https://rockstor.com/docs/howtos/15-3_to_15-4.html
or the similar earlier howto first if you are still on a 15.2 base, if you are that far back. Mixed raid doesn’t need kernel backports when on 15.4.
Testing Changelog reference for when mixed raid levels were added in Rockstor:
But you might as well be on 4.6.0-0 which is available in testing from 9 days ago. See later on in the above referenced forum thread.
So given metadata is likely the main slow-down on the parity raid side, you could consider doing a Resize/ReRaid on that pool:
to say “raid5-1”: our nomenclature for data = brtrfs-raid5 with metadata btrfs-raid1:
And once the associated balance has finished (again could still take quite some time) the result should be reflected in the Pool details here:
Obviously this is a non trivial modification of live data, so refresh back-up before hand.
But as you likely already know the system can be used, mostly as normal, during this operation. There will of course be some drive subsystem bandwidth and CPU busied by the event.
Yes, no worries there. Just info after a qgroup rescan.
You can always start it off again.
Hope that helps.