@nfriedly The “… too many open files …” issue is a bad one as it can randomly break any number of things across the entire system related to the volume in question. Not just Rockstor related. Also of note is that disabling quotas is very invasive and can lead to undetermined behaviour. There have, however, been a number of fixes in the current testing channel that may be relevant. Most notable of these were both merged a month ago in:
With the most relevant, from a functionally perspective, being:
while the other in that release is a useful addition that reports all current pool and share mount options in all relevant tables and pool/share detail views.
Due to the relatively frequent stable releases, which contain all ‘to-date’ at the time of release testing channel fixes, testing channel release fixes are very rarely ‘back ported’. And the testing channel is mostly assumed when assisting with development.
Hope that helps and there is also a pending pr that improves subvol mount robustness re degraded pool scenarios.
However, given all of that, I would first check your pool health as if it has gone Read-only that can also break subvol (share) mounts: at least for released Rockstor code anyway as that was the subject of my pr today. But I do appreciate that you have a chicken and egg scenario here given your system is affected by the “… too many open files …” scenario. Tricky.
as that was the subject of my pr today. But I do appreciate that you have a chicken and egg scenario here given your system is affected by the “… too many open files …” scenario. Tricky.