Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

7
  • Yes, btrfs check --repair after a backup seems the most viable and sensible solution. I recommend the OP use something such as Clonezilla for backing up the whole partition or btrfs-clone for copying the filesystem (better option). Commented Aug 2 at 3:09
  • I’m interested in trying what you suggested. I am getting matching contradictory info from multiple disk checker programs but probably worth trying to repair if it’s quick, safe, and easy. I am a little unsure if I have an LVM with some free space in a VG but I think so. df shows my Use% as 26% and everything else is the same (except for the Mounted on which is / for one and /home for the other) for the same file system on 2 lines of output. pvdisplay, vgdisplay and lvdisplay show nothing probably because of the read only filesystem. Commented Aug 19 at 18:58
  • 1
    @GrowingMyRoots If pvs does not show anything then you do not have LVM (or it is broken, configured in a way that it does not find the PVs). If you do not have any spare storage then you can try using RAM as CoW volume; usually not that much is written by fsck. So either create a block ram disk (dev/ram0, modprobe brd ...) or create a file in tmpfs (/dev/shm) and set up a loop device on top of it (losetup). Commented Aug 20 at 4:01
  • 1
    @GrowingMyRoots Of course, they copy the entire system, and thus the packages as well. btrfs-clone has the advantage of reconstructing the btrfs filesystem in the target filesystem. Commented Aug 25 at 0:15
  • 1
    @horsey_guy Great thank you. I think all of these would be better than my current home directory backup Commented Aug 25 at 17:47