I would run a check, then balance, then see if it's still throwing errors. It sounds like something has caught, but if there's an errant snapshot I wouldn't worry about it.
Linux
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
sudo mount -o subvolid=5 /dev/<your disk here> /mnt
This will give you full access to the filesystem, then you can identify the full path of snapshots and delete them ie.
sudo btrfs subvolume delete /mnt/...
In openSUSE, snapper works by booting to a snapshot. "mount" command will reveal which subvolume you are booted from.
Thanks for the answer! I mounted it and removed all the timeshift-btrfs stuff. now, after a reboot, sudo btrfs subvolume list -t /
does not show timeshift stuffs anymore, but if I mount again sudo mount -o subvolid=5 /dev/nvme0n1p2 /mnt
and ls /mnt/
I get:
@ @cache @home @log timeshift-btrfs
how can I remove timeshift-btrfs
from there? can i just rm -rf
it?
In openSUSE
(sorry I forgot to mention, I'm running EndeavourOS)
Make sure it doesn't have anything valuable. Use rm -rf
It worked, thank you very much for your help man! Now the only remaining problem is the snapshot 166, that snapper does not let me remove. I assume I should remove in a similar way as timeshift:
$ sudo btrfs subvolume delete /.snapshots/166/snapshot
WARNING: not deleting default subvolume id 2968 '/.snapshots/166/snapshot'
I think there's something I'm missing about how these snapshot works
The snapshot may be mounted to root. In the output of "mount" command, if there isn't a subvolid= or subvol= parameter for root mount, snapshot 166 is currently mounted to root.