Could you clarify that a little I’m not quite sure what you mean. I’d also like to know if the nvme system disk showing as missing fix has worked for you, at your convenience of course. I.e. is your nvme sys disk now showing up ok and not as detached !
As per the fix, it may only take effect after a full reboot unfortunately and as I have no real nvme system here I unfortunately couldn’t fully replicate your setup. But I did add a unit test to help guard against this particular regression resurfacing and based it on the command output you provided (thanks for that).
Hope that helps and let us know what your current systems state is so we can pick it up from there.
Thanks again for reporting this and I hope that this newer version has at least moved us forward a tad. The system disk detection is a bit of a tricky area for us currently and is in need of some cleanup so we will just have to improve that area bit by bit. It still has some legacy mechanisms that need to be moved to a newer system we established for the non system drives.
Yes I was going to suggest the immutable flag as we still have a bug or two around it’s use. We use it to avoid writes when a mount fails ‘silently’, ie there isn’t inadvertent writing to the mount point rather than the usual share (when it’s not mounted).
Anyway definitely a bug or two left but I did sort one like this recently:
I’ll try and do a code audit of our immutable flag use and get this in better shape, and if not at least create a technical wiki entry on our use of it to help clear things up going forward.
Thanks for your patience and perseverance; and I hope you enjoy your newly non-detached nvme system disk, complete with resident rockon share.
By the way, did you know you can enable / disable quotas from a Pool’s details page or the Pools page:
