@jmangan Hello again.
It may be that a reboot, which effects a full unmount and remount, may help here. There are certain situations where this can help. Also can you confirm which version of Rockstor this is, i.e. you stated previously:
This is fairly up to date from our core code point of view but very old from our base OS point of view and the kernel btrfs stack perspective. Which is what you are exercising mainly when doing btrfs opperations. You may well benefit from the years of development in these stacks that is represented as a difference between our CentOS variant (pending legacy status) and our newer, still in release candidate 5 state, Rockstor 4 variant which is based
‘Built on openSUSE’ Leap 15.2 and so has far newer btrfs kernel stack components.
Unfortunately no installer download as of yet but you can build your own with all updates pre-installed via the following repos instructions:
Note however that this version has broken AD/LDAP but we do have a pending fix which we hope to review and integrate in the testing channel for that release in the near future.
Hope that helps. Also note that scrub and balance opperations can take a few goes to do their thing. So always worth trying again, especially after a clean mount (read reboot). Also these operations, balance mainly thought, can suffer from a lack of memory. You mention running on a depleated memory due to the bad stick so again you could try again once you have installed the new stick/sticks.
Let us know how it goes and glad to here that you have sorted at least some of the resulting side effects of running with bad ram. It’s more common than folks appreciate and very difficult for any file system to protect itself against. Hence the common recommendation for ECC memory on mission critical deployments.
Hope that helps.