I recently added snapd to my server and used it to install an application. That all went perfectly and everything there is running fine.
My problem is that snapd installs the app in a mounted squashFS partition which is read-only and 100% full. Great for optimizing the install but it triggers endless Critical errors:
"The filesystem “/var/lib/snapd/snap/core/6405” mounted at “/var/lib/snapd/snap/core/6405” reached “critical” status because you currently use 100% of its available inodes."
Being full in this instance is not dangerous because you can't write to the partition. It's marked read-only. It just holds the code for the app.
What I need is some way to disable the error _without_ disabling it for the other drives and partitions. Disabling warnings here appears to be an all or nothing affair.
For future enhancement perhaps disable disk full errors on partitions marked read-only.
My problem is that snapd installs the app in a mounted squashFS partition which is read-only and 100% full. Great for optimizing the install but it triggers endless Critical errors:
"The filesystem “/var/lib/snapd/snap/core/6405” mounted at “/var/lib/snapd/snap/core/6405” reached “critical” status because you currently use 100% of its available inodes."
Being full in this instance is not dangerous because you can't write to the partition. It's marked read-only. It just holds the code for the app.
What I need is some way to disable the error _without_ disabling it for the other drives and partitions. Disabling warnings here appears to be an all or nothing affair.
For future enhancement perhaps disable disk full errors on partitions marked read-only.