#3343 Issue closed: Fedora Linux 41 (Silverblue): Disable /dev/zram0 in disklayout.conf

Labels: enhancement, fixed / solved / done

gdha opened issue at 2024-11-09 15:57:

  • ReaR version ("/usr/sbin/rear -V"):
    Relax-and-Recover 2.7

  • If your ReaR version is not the current version, explain why you can't upgrade:
    n/a

  • OS version ("cat /etc/os-release" or "lsb_release -a" or "cat /etc/rear/os.conf"):
    Fedora Linux 41.1.4 (Silverblue)

  • ReaR configuration files ("cat /etc/rear/site.conf" and/or "cat /etc/rear/local.conf"):

OUTPUT=RAMDISK
OUTPUT_URL=file:///boot
BACKUP=EXTERNAL
FIRMWARE_FILES=( 'no' )
KERNEL_FILE="/boot/ostree/fedora-e3c1d1d259dc0f5dfd87e0c8a3f31e7233b33ba091986f069aa8cb579b2aa37c/vmlinuz-6.11.4-301.fc41.x86_64"
COPY_AS_IS+=( /usr/lib64/systemd/libsystemd-shared-256.7-1.fc41.so )
REQUIRED_PROGS+=( chattr )
PROGS+=( lsattr )

  • Hardware vendor/product (PC or PowerNV BareMetal or ARM) or VM (KVM guest or PowerVM LPAR):
    x86_64 VM

  • System architecture (x86 compatible or PPC64/PPC64LE or what exact ARM device):
    x86

  • Firmware (BIOS or UEFI or Open Firmware) and bootloader (GRUB or ELILO or Petitboot):
    UEFI grub2

  • Storage (local disk or SSD) and/or SAN (FC or iSCSI or FCoE) and/or multipath (DM or NVMe):
    /dev/sda

  • Storage layout ("lsblk -ipo NAME,KNAME,PKNAME,TRAN,TYPE,FSTYPE,LABEL,SIZE,MOUNTPOINT"):

# lsblk -ipo NAME,KNAME,PKNAME,TRAN,TYPE,FSTYPE,LABEL,SIZE,MOUNTPOINT
NAME        KNAME      PKNAME   TRAN   TYPE FSTYPE LABEL        SIZE MOUNTPOINT
/dev/sda    /dev/sda            sata   disk                      15G 
|-/dev/sda1 /dev/sda1  /dev/sda        part vfat                600M /boot/efi
|-/dev/sda2 /dev/sda2  /dev/sda        part ext4                  1G /boot
`-/dev/sda3 /dev/sda3  /dev/sda        part btrfs  fedora_vbox 13.4G /var/home
/dev/sr0    /dev/sr0            ata    rom                     1024M 
/dev/zram0  /dev/zram0                 disk                     1.9G [SWAP]

  • Description of the issue (ideally so that others can reproduce it):
    recreation of /dev/zram0 would fail in recover mode

  • Workaround, if any:
    n/a

  • Attachments, as applicable ("rear -D mkrescue/mkbackup/recover" debug log files):

# tail -1 /var/lib/rear/layout/disklayout.conf 
swap /dev/zram0 uuid=7857a6eb-a78f-4ae0-a609-5905bed86012 label=zram0

gdha commented at 2024-11-13 08:12:

Moved the milestone to "3.0" as Fedora Silverblue has bigger issues than /dev/zram.
The BTRFS sub-volumes seems to use a FUSE overlay file system which ReaR cannot deal with.

jsmeix commented at 2024-11-13 08:19:

Sigh!

It seems also Fedora moves towards
an (over)sophisticated btrfs filesystem :-(

Cf.
https://en.opensuse.org/SDB:Disaster_Recovery
(excerpts)

The simpler the system, the simpler and easier the recovery.
...
In the end when it comes to the crunch your elaborated and
sophisticated system will become useless when you cannot
recreate it with your disaster recovery procedure.

jsmeix commented at 2024-12-12 14:36:

Only as a side note FYI:
Regarding btrfs on Fedora Workstation see
https://github.com/rear/rear.github.com/pull/22#issuecomment-2539026311

github-actions commented at 2025-02-11 02:36:

Stale issue message

gdha commented at 2025-03-17 14:58:

@pcahyna Could you confirm it is okay to exclude zram swap (on Fedora Silverblue and perhaps other Fedora variants) from the disklayout.conf file?

gdha commented at 2025-03-28 08:45:

With PR #3343 merged we can close this issue.

[Export of Github issue for rear/rear.]