> On Mar 23, 2017, at 8:40 AM, [email protected] wrote:
>
> Greetings.
>
> I've been using Amanda 3.3.7 for a while with no problems. I'm building
> a new machine, and I installed Amanda 3.4.3 .
>
> I'm having a problem backing up file systems that have mounted file systems
> under them. For example, I have these two disks mounted:
>
> /dev/sda4 on /boot type ext4 (rw)
> /dev/sda1 on /boot/efi type vfat (rw)
>
> and I have this DLE:
>
> alfred /boot simple-gnutar-local
>
> The backup process hangs. However, as soon as I umount /boot/efi, the
> backup runs perfectly. If I remount /boot/efi, then the backup will
> hang again.
>
> I'm not sure exactly where it's hanging. The only troubleshooting info
> I have at this time is that the incremental file
> /usr/local/var/amanda/gnutar-lists/alfred_boot_0.new
> is created but size zero. My best guess, at this time, is that tar is
> printing a warning to stderr:
>
> /bin/tar: ./efi: directory is on a different filesystem; not dumped
>
> and this is perhaps somehow confusing amanda. But I have no idea if that's
> true.
>
> I didn't have this problem on the old machine.
>
> If anybody has some advice, either to fix or to troubleshoot, I'd appreciate
> it.
>
> --hymie! http://lactose.homelinux.net/~hymie [email protected]
> My fitbit says I've walked 1817 steps today (as of 09:16).
This is mostly a BUMP to your original question. I’m not on amanda 3.4.x yet,
but under 3.9.x,
I regularly get these
/bin/tar: ./efi: directory is on a different filesystem; not dumped
type of error messages, and the dump continues quite happily.*
* Yes, I could use amgtar to make amanda stop telling me about those. I just
haven’t done
so yet.
Deb Baddorf
Fermilab
