That is why snaps suck donkey balls.
They don't go away on their own, every installed snap is mounted as its own loop device and snapd keeps an older revision or two so it can roll back, so the number moves around after updates. snap list --all shows which snaps they are, if one says disabled that's the old revision and you can remove it with sudo snap remove <name> --revision=<rev>. about libation, if it's installed as a snap itself that could be the actual problem, snaps are confined and can't read folders outside your home or on other drives unless you connect the removable-media interface, so I'd check that before worrying about the loop devices.
Awesome! That was going to be the next thing I looked up was how to do the snap list. It shouldn't be impacting my libation as that is running in a docker instance managed by portainer. Though now that I think back I had initially installed libation using snap, but couldn't get it to work, so perhaps I have both instances running and am trying to use the snap one on accident when I need to be opening the docker instance.
If the backing files are referencing "snapd", then it seems plausible that these are the sandbox filesystems for software packaged using the Snap environment.
Okay, I have used snap to install things before but it never generated these faux disks that I can't seem to delete. Would you guess that it is a temporary issue and a restart should resolve? (haven't restarted yet because I have been using the audiobookshelf and plex and haven't scheduled a maintenance window yet)
What makes you think it's an issue? What problem is it causing? You can probably identify which snap they belong to.
I don't know for certain that these unexpected devices in my disk manager are causing the issue, but I noticed them at the same time as the issue with libation being unable to access the directory it normally uses and so I may be conflating 2 unrelated issues
I believe you are conflating two unrelated things. Snap regularly creates those devices, it’s normal, required for snaps to work, and nothing to worry about at all.
Oh okay, so do they go away on their own or do they persist potentially indefinitely? I have used snap in the past but had never noticed these until now. I guess I was just paranoid after the plex vulnerability news haha. Thanks.
You are just seeing the remains of snapd
Loop devices are just files mapped as block devices. Snaps cordon off an area on disk for install and config, you should probably see more than one per app if you updated, that's how snaps can be reverted to previous versions. You can set how many versions snaps keep per app.
That makes sense, are they intended to persist indefinitely, only while the subject application is running, or do they go away after a period of time? Thanks for your help!
I have limited exposure to snaps, but from my experience, the oldest eventually gets overwritten by newer ones.
Selfhosted
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil.
-
No spam.
-
Posts are to be related to self-hosting.
-
Don't duplicate the full text of your blog or readme if you're providing a link.
-
Submission headline should match the article title.
-
No trolling.
-
Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.
-
AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!