Error: ENOENT: no such file or directory, mkdir '/var/snap/firefox/common/host-hunspell/.Trash-1000'
What became clear after some investigation was, that all my files (under /common/... and /depot/... I do like work outside my home dir 😬) have a devId of 64768 (nothing wrong with that…), but that that ID is given twice (!) in the list coming from procfs!
The first one looks sane (my “root mount“) the second doesn't. Reboot didn't help by the way.
I did two fixes (each one having effect in my case)
• first one wins (won't get „wiped“), so far last one won. – of course it's a gamble, if the more correct mount is truly listed earlier
• filter out 'snaps' (and while we're at it several others, like /proc, /proc/, /proc/something… but not /procedures (perhaps that's a valid mount, eh?)
The result looks good on my machine (essentially like df, not missing anything. (nb: I do have LUKS encryption, distinct boot partition and a Samba-share, all good, all there)
Original bug encountered (Ubuntu-MATE 22.04)
What became clear after some investigation was, that all my files (under
/common/...
and/depot/...
I do like work outside my home dir 😬) have a devId of 64768 (nothing wrong with that…), but that that ID is given twice (!) in the list coming from procfs!The first one looks sane (my “root mount“) the second doesn't. Reboot didn't help by the way.
I did two fixes (each one having effect in my case) • first one wins (won't get „wiped“), so far last one won. – of course it's a gamble, if the more correct mount is truly listed earlier • filter out 'snaps' (and while we're at it several others, like
/proc
,/proc/
,/proc/something…
but not/procedures
(perhaps that's a valid mount, eh?)The result looks good on my machine (essentially like
df
, not missing anything. (nb: I do have LUKS encryption, distinct boot partition and a Samba-share, all good, all there)