Did a snapper rollback entirely, root system. Then rebooted and got a warning about read-only or something. It's working without issues but not creating any new snapshots when I check sudo snapper list even though the config is there and in btrfs subvolume list they show up. Can't create any new snapshots manually, I suspect it's a mounting issue because it yields a IO Error (.snapshots is not a btrfs subvolume). when I try.
Seems like .snapshots is not being recognized even though it seems to be mounted. I don't want to mess with /etc/fstab to not risk making it worse. Any recommendations?
#Snapper
mighty grotto
blissful karma
Use arch live USB take a writable snapshot from the read-only snapshot and set the writable snapshot as root subvolume.
mighty grotto
I can boot without issues and managed to solve the manual and automatic snapshots by deleting the subvolume and doing a btrfs command to create a new one. My main issue is that the snapshots seem to be filling up my root directory
technically, I checked it with snapper enable quota / they are currently just taking a few MiB worth of space but shows as a lot in every disk management tool.
I tried doing btrfs subvolume delete /.snapshots/1636/snapshot rm -rf /.snapshots/ but isn't letting me.
When I do btrfs subvolume list / I get lots of snapshots that should have been deleted (deleted the original .snapshots subdirectory and created new one so they don't show up on snapper list) and they all seem to be nested upon each other in a weird config because months ago I had a problem with snapshots.
ID 256 gen 1154227 top level 5 path var/lib/portables
ID 257 gen 1154227 top level 5 path var/lib/machines
ID 258 gen 1155073 top level 5 path .snapshots
ID 436 gen 1154227 top level 258 path .snapshots/178/snapshot
ID 437 gen 1154229 top level 436 path .snapshots/178/snapshot/.snapshots
ID 2102 gen 287416 top level 437 path .snapshots/178/snapshot/.snapshots/1635/snapshot
ID 2103 gen 288388 top level 437 path .snapshots/178/snapshot/.snapshots/1636/snapshot
ID 2113 gen 289092 top level 437 path .snapshots/178/snapshot/.snapshots/1646/snapshot
ID 2125 gen 289683 top level 437 path .snapshots/178/snapshot/.snapshots/1658/snapshot
ID 2153 gen 291383 top level 437 path .snapshots/178/snapshot/.snapshots/1685/snapshot
ID 2161 gen 291848 top level 437 path .snapshots/178/snapshot/.snapshots/1693/snapshot
ID 2163 gen 291875 top level 437 path .snapshots/178/snapshot/.snapshots/1695/snapshot
ID 2164 gen 291998 top level 437 path .snapshots/178/snapshot/.snapshots/1696/snapshot
ID 6183 gen 1113937 top level 258 path .snapshots/4197/snapshot
ID 6782 gen 1152274 top level 258 path
it isn't letting me send the rest because it's marked as spam detected by the server. But similar thing, keep happening even when I deleted some so it went back to 1,2, 6... and at the bottom, the ones that are correct and actual snapshots being automatically backed up as intended and deleted periodically. It's the ones above that I suspect are taking up too much space but I can't find them
wintry thistle
it isn't letting me send the rest because it's marked as spam detected by the se...
use a paste service or upload as .log/.txt
mighty grotto
I just deleted 3 GiB worth of other files through ncdu / but still appears as the exact same space as before on my root partition so there's some issue here. Is it the snapshots?
and this persists through reboot. I did it mostly to text if it still shows up the warning after booting with being read only or something
I also have grub-btrfs but last time I tried I couldn't boot into them, sent me to rootfs probably being read only so those are probably not working properly. At least the old ones, haven't tried with the ones generated since I fixed the .snapshots subdirectory with the command. I guess I have to sync them manually now? Generate a new grub config?