and @Thailgrott
I agree with @Flox these could all be snapshot / subvol count related in cohorts with quotas enabled.
Also, if attempting to reduce snapshot counts, that the delete of a snapshot is the expensive part. The creation is essentially free. So if your pools have ground to a halts, or near enough, just try disabling quotas, either via the Web-UI:
or via the command line if the Web-UI is misbehaving potentially due to ‘hangs’ caused by quota issues.
btrfs quota disable /mnt2/pool-name
Best turn off quotas first before attempting any share / snapshot removal, they are both subvolumes, as it’s a lot less expensive to do this when quotas are not enabled.
Hopefully this will help, and given you are both on > 3.9.2-18 all function, bar share size reporting, should work as expected.
Definitely worth a try I recon as many have reported vast speed ups with quotas disabled and I’ve had to do the same on an older pool I have here just to return it to ‘proper’ function. It would slow to a crawl and then ‘break’ associated things due to time outs. Bit frustrating but we are only moving forward with such things and there are many fixes awaiting us in this area, and others, as the btrfs devs are making great strides as time goes on.
Let us know how a quota disable works out before you try anything else as particularly the slow ‘ls’ report is a potential give away on this one, which in turn would hold up some docker images as well.