People,
A while ago I was in a hurry to start using F40 (Sway) and installed
Rawhide from a live usb to get started.
Everything went pretty well and I had minimal problems up until after
f40 was release. However now, when I tried to do a:
dnf system upgrade download --releasever=40
I get a lot of errors - trying to do "dnf --erase" the problem rpms ends
up making the problem worse.
You need to tell us what errors you encounter. Are they filesystem problems,
package conflicts, etc.?
So, if I try to reinstall from the current f40 live usb - can I do that
without touching the backup subvolume? ie:
/dev/nvme0n1p3 btrfs 1,951,850,496 464,659,184 1,486,438,224
24% /
/dev/nvme0n1p3 btrfs 1,951,850,496 464,659,184 1,486,438,224
24% /backup
Unlike earlier filesystems, btrfs doesn't silently ignore bitrot. Corrupt btrfs filesystems
are often a result of hardware faults.
For decades I have just been using a separate partition for /home with
ext[2|3|4] and this was conveniently not touched if I did a custom
install to upgrade - I want to do something similar for this backup
subvolume.
I would never consider a btrfs subvolume a suitable location for a backup. The btrfs
snapshots provide a way to go back in time after data are lost due to a software
glitch or command-line typo. Using a subvolume, when the drive fails, both the original
and backups may be lost. If a drive is close to failure, a linux install often pushes
it over the edge (due to amount of activity), so I like to make sure backups are good before
an upgrade or install.