#2959 Issue closed: ZFS Filesystems are not backed up

Labels: enhancement, needs sponsorship, external tool, no-issue-activity

mainjoehere opened issue at 2023-03-23 14:30:

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

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

Distributor ID: Debian
Description:    Debian GNU/Linux 11 (bullseye)
Release:    11
Codename:   bullseye
  • ReaR configuration files ("cat /etc/rear/site.conf" and/or "cat /etc/rear/local.conf"):
OUTPUT=ISO
BACKUP=NETFS
BACKUP_URL="nfs://192.168.1.144/media/storage/rear"

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

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

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

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

NAME        KNAME     PKNAME   TRAN TYPE FSTYPE     LABEL  SIZE MOUNTPOINT
/dev/sda    /dev/sda           spi  disk                   100G 
|-/dev/sda1 /dev/sda1 /dev/sda      part                  1000K 
|-/dev/sda3 /dev/sda3 /dev/sda      part zfs_member bpool    1G 
`-/dev/sda4 /dev/sda4 /dev/sda      part zfs_member rpool 98,7G 
/dev/sr0    /dev/sr0           ata  rom                   1024M 
/dev/zd0    /dev/zd0                disk swap                4G [SWAP]

zpool list
NAME    SIZE  ALLOC   FREE  CKPOINT  EXPANDSZ   FRAG    CAP  DEDUP    HEALTH  ALTROOT
bpool   960M   660M   300M        -         -    52%    68%  1.00x    ONLINE  -
rpool  98.5G  78.5G  20.0G        -         -    73%    79%  1.00x    ONLINE  -

zfs list
NAME                   USED  AVAIL     REFER  MOUNTPOINT
bpool                  659M   172M       96K  /boot
bpool/BOOT             646M   172M       96K  none
bpool/BOOT/debian      646M   172M      222M  /boot
rpool                 82.7G  12.8G      192K  /
rpool/ROOT            23.0G  12.8G      192K  none
rpool/ROOT/debian     23.0G  12.8G     6.75G  /
rpool/home            50.0G  12.8G      364K  /home
rpool/home/mainzer    49.7G  12.8G     22.9G  /home/mainzer
rpool/home/root        326M  12.8G      298M  /root
rpool/opt             4.61G  12.8G      766M  /opt
rpool/srv             4.64M  12.8G      488K  /srv
rpool/swap            4.25G  17.0G     51.3M  -
rpool/tmp             13.6M  12.8G     13.6M  /tmp
rpool/usr             49.4M  12.8G      192K  /usr
rpool/usr/local       49.2M  12.8G     38.5M  /usr/local
rpool/var              417M  12.8G      192K  /var
rpool/var/games        192K  12.8G      192K  /var/games
rpool/var/lib          596K  12.8G      192K  /var/lib
rpool/var/lib/docker   192K  12.8G      192K  /var/lib/docker
rpool/var/lib/nfs      212K  12.8G      212K  /var/lib/nfs
rpool/var/log          385M  12.8G      106M  /var/log
rpool/var/mail         192K  12.8G      192K  /var/mail
rpool/var/snap         192K  12.8G      192K  /var/snap
rpool/var/spool       29.9M  12.8G     3.77M  /var/spool
rpool/var/www          192K  12.8G      192K  /var/www
  • Description of the issue (ideally so that others can reproduce it):

rear does not backup any of the above filesystems

cat var/lib/rear/layout/disklayout.conf 
# Disk layout dated 20230323150044 (YYYYmmddHHMMSS)
# NAME        KNAME     PKNAME   TRAN TYPE FSTYPE     LABEL  SIZE MOUNTPOINT UUID                                 WWN
# /dev/sda    /dev/sda           spi  disk                   100G                                                 
# |-/dev/sda1 /dev/sda1 /dev/sda      part                  1000K                                                 
# |-/dev/sda3 /dev/sda3 /dev/sda      part zfs_member bpool    1G            10832798754208484787                 
# `-/dev/sda4 /dev/sda4 /dev/sda      part zfs_member rpool 98.7G            18140521004606291834                 
# /dev/sr0    /dev/sr0           ata  rom                   1024M                                                 
# /dev/zd0    /dev/zd0                disk swap                4G [SWAP]     648730e3-9102-40b7-ad9a-b38be26c67e0 
# Disk /dev/sda
# Format: disk <devname> <size(bytes)> <partition label type>
#disk /dev/sda 107374182400 gpt
# Partitions on /dev/sda
# Format: part <device> <partition size(bytes)> <partition start(bytes)> <partition type|name> <flags> /dev/<partition>
#part /dev/sda 1024000 24576 rear-noname bios_grub /dev/sda1
#part /dev/sda 1073741824 1048576 rear-noname none /dev/sda3
#part /dev/sda 105925210112 1074790400 rear-noname none /dev/sda4
# Filesystems (only ext2,ext3,ext4,vfat,xfs,reiserfs,btrfs are supported).
# Format: fs <device> <mountpoint> <fstype> [uuid=<uuid>] [label=<label>] [<attributes>]
# Swap partitions or swap files
# Format: swap <filename> uuid=<uuid> label=<label>
swap /dev/zd0 uuid=648730e3-9102-40b7-ad9a-b38be26c67e0 label=

jsmeix commented at 2023-03-23 14:37:

In general:
ZFS is not (yet?) supported by ReaR, see
https://github.com/rear/rear/issues/2773
and
https://github.com/rear/rear/issues/1932
and
https://github.com/rear/rear/issues/2563

pcahyna commented at 2023-03-23 14:46:

When (if?) ZFS gets supported by ReaR, it will probably have analogous issues (#2928 #2604) as btrfs has with backing up data from subvolumes, as ZFS filesystems are IIUC analogous to btrfs subvolumes.

github-actions commented at 2023-05-23 02:22:

Stale issue message

[Export of Github issue for rear/rear.]