/var/snap mounted on a logical volume, and experienced the case today that, despite unmounting
/var/snap, i was unable to fsck the logical volume until i stopped the
.mount systemd unit associated with a
nsfs mount type.
The nsfs entry in question:
nsfs on /run/snapd/ns/mysnap.mnt type nsfs (rw)
I would get
Logical volume ... is in use,
fuser returned nothing.
Snapd was not running, and neither were any daemons within snaps.
- How to tell which of the nsfs mounts is holding on to which filesystem / volume?
- When i umount the nsfs entry myself, it gets re-created the next time i snap start the service. So why does it not gets cleaned up automatically when I snap stop the service?
That would line up with my mental model / expectation that when neither snapd nor any snap services are running, nothing is holding on to the volume underlying