pcahyna

I have experimented with the LFTP-dependent backup schemes (sftp is among them) some time ago and I dimly recall that it was not easy (maybe even impossible) to stop lftp...

it is also related to the change done by @lzaoral recently. If a working serial console is detected on your machine, it is used as `/dev/console`.

https://github.com/rear/rear/blob/edbe2ee9de54ed4e98424094c71bf4a7ba6bd69a/usr/share/rear/lib/serial-functions.sh#L47-L54

> If an executable program loads a library via dlopen > that additional library must be specified in LIBS > and then all libraries that are "normally" linked with >...

@gdha do you know how do the loop devices get skipped? I don't see any code to skip them under `layout/save`. There is code in 200_partition_layout.sh that skips generating `disk`...

@david-hill could you please provide the `/var/lib/rear/layout/disklayout.conf` file generated when you got the error?

@gdha I don't see that: ```sh dd if=/dev/zero of=/var/tmp/loopfs bs=1024 count=102400 mkfs.xfs /var/tmp/loopfs mkdir /home/loopfs mount -o loop /var/tmp/loopfs /home/loopfs rear savelayout ``` results in this in layout: ``` fs...

@david-hill your issue is only tangentially related to loop devices. Using a PV/VG on a disk: ```bash parted --script -a optimal /dev/vdc -- mklabel gpt mkpart extra ext2 1M -1M...

What to do with loop devices is a separate question, but I think should be addressed consistently for all storage objects on them (you see above that filesystems on loop...

Why shouldn't be any useful data on /dev/loop ? Is it because the backing files of loop devices can be already saved when the filesystem where they reside is backed...