@Mike-B Hello again.
Re:
Apologies for not providing that previously. I was a bit distracted with the 5.0.13-0 release (now out).
As the root user run:
btrfs quota disable /mnt2/Master-Pool
Then re-enable the quotas via the Web-UI in the Master-Pool details view.
You may have to login (if using the Web-UI embedded shell) using your Web-UI admin user (a regular user), then su command to gain super user (root) status. Local terminal access accepts root user login just dandy without needing this run-around via the su command.
The initial command line quota disable is precautionary as we have seen imported pools end up in an intermediate quota state that confuses the Web-UI. Disabling first via CLI then re-enabling in the Web-UI seems to set things straight. Our quota support within the Web-UI is fledgling at best: but we did have an update in the latest testing release on this front (just now actually) via 5.0.13-0:
that fixes Web-UI Share Resize, as after importing a Pool all its shares end up at the size of the host Pool: which is distracting. I.e. all your shares are showing this as they are 4.55 TB. It’s currently only cosmetic but still distracting.
Once you have re-enabled quotas on the Pool it will take possibly a few minutes to re-establish what size is actually taken up by the data that we hope is still there. A page refresh or two should start to indicate a non-zero share size as it tallies up the individual usage via the quota system.
As always keep us posted and keep the feedback coming: all good.
Hope that helps.