Re: [Bug-tar] I don't know why tar-1.27 cannot back up the contents of a softlink

[Pavel Raiskup]

Gene, thanks for details.

On Friday 25 of July 2014 05:53:47 Gene Heskett wrote:
> I don't think we are exactly on the same page. After 2 or 3 backups by
> amanda, I am still looking at a refusal to handle softlinks, which
> should be backed up by including the link data.
>
> So I am still looking at this in my amdump backup reports:
>
> STRANGE DUMP DETAILS:
> ....
>   ? /usr/bin/tar: ./run: directory is on a different filesystem; not
> dumped
>   ? /usr/bin/tar: ./lib/nfs/rpc_pipefs: directory is on a different
> ...

Amanda seems to call tar with --one-file-system, which is most probably
desired behavior... If those missing files causes your troubles, this is
not about GNU tar bug, I suppose.

> Now, according to fdisk:
> [....]

Not only /dev/sda filesystems are mounted on your system.  For more info
you should probably try the `mount` command which lists for you all
mounted filesystems.

Anyway, if we are talking about some temp filesystems (or something like
that), you usually don't want to backup them.  There are tools responsible
for creating temporary structures (e.g. systemd-tmpfiles --create if your
system runs systemd).

> FWIW, I just now applied that patch, then did a make clean;make
> which bails out now:
> [...]
> WARNING: 'automake-1.14' is missing on your system.
>          You should only need it if you modified 'Makefile.am' or
> [...]

That is expected, attached patch is done against git version (for
next-release purposes).  If you wan't to use it, you must first
'autoreconf -vi'.  Of course, as I said before - it is enough firstly run
'make check' and than 'make distcheck' (as in this order it is also
mentioned in INSTALL file).

Pavel