Hi, as you already wrote, /boot/efi is a mount point for a partition of the flash memory of your main board, so it is in fact a different file system, not a symlink or such. If I understood it correctly, the partition is formatted with a vfat-like file system and holds boot images etc. for your machine. I'm in doubt that it makes sense to include this stuff in a backup. Even if you need to do a bare-iron recovery of that machine, you probably would first re-install the OS, what would update that partition with your new boot image anyway. So I would go with a simple exclude statement for /boot/efi in the disklist.
Jens On Thu Dec 21 2017 10:49:26 GMT+0100 ghesk...@shentel.net (Gene Heskett) wrote: > Greetings; > > I added another small machine to my disklist last night, but got this > error reported this morning: > > STRANGE DUMP DETAILS: > /-- rock64 /boot lev 0 STRANGE > sendbackup: start [rock64:/boot level 0] > sendbackup: info BACKUP=/bin/tar > sendbackup: info RECOVER_CMD=/bin/tar -xpGf - ... > sendbackup: info end > ? /bin/tar: ./efi: directory is on a different filesystem; not dumped > | Total bytes written: 51466240 (50MiB, 6.7MiB/s) > sendbackup: size 50260 > sendbackup: end > \-------- > > The amanda-client is from a debian-arm stretch repo. > Do I just need to exclude it in the /boot recipe, and make a 3rd disklist > entry just for it? But an ls -l does not show it as a linked directory. > Prowling around in it, there is not a single hint that failed directory > is anything but a normal ext3-4 subdirectory. > > However a mount report says this: > /dev/mmcblk1p6 on /boot/efi type vfat > (rw,relatime,fmask=0022,dmask=0022,codepage=936,iocharset=utf8,shortname=mixed,errors=remount-ro) > > So it does look like I need to adjust the disklist after all? > > > > Cheers, Gene Heskett >
