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

[Gene Heskett]

On Friday 25 July 2014 10:27:15 Pavel Raiskup did opine
And Gene did reply:
> 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.
> 
I will ask on the amanda list, about the desirability of that, thank you.

> > 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.

address@hidden:/var/log/apache2# mount
/dev/sda2 on / type ext4 (rw,errors=remount-ro)
proc on /proc type proc (rw,noexec,nosuid,nodev)
none on /sys type sysfs (rw,noexec,nosuid,nodev)
none on /sys/kernel/debug type debugfs (rw)
none on /sys/kernel/security type securityfs (rw)
none on /dev type devtmpfs (rw,mode=0755)
none on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=0620)
none on /dev/shm type tmpfs (rw,nosuid,nodev)
none on /var/run type tmpfs (rw,nosuid,mode=0755)
none on /var/lock type tmpfs (rw,noexec,nosuid,nodev)
none on /lib/init/rw type tmpfs (rw,nosuid,mode=0755)
/dev/sda1 on /boot type ext3 (rw)
/dev/sdc2 on /amandatapes type ext3 (rw)
rpc_pipefs on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw)
binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc 
(rw,noexec,nosuid,nodev)

and 2 more remote nfs mounts which are not germane to this.
> 
> 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).
> 
I haven't managed to get corralled into that mess of spaghetti yet.

> > 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'. 

I had to add the --force option.

> 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).
> 
And that worked moderately well until I gave that famous moose a goose.  
Most tests then passed.

However, even the command you suggested now results in a make exit in 
about 15 lines.  I'll have to unpack it again after saving that patch 
someplace else.

> Pavel

Thanks Pavel.

Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page <http://geneslinuxbox.net:6309/gene>
US V Castleman, SCOTUS, Mar 2014 is grounds for Impeaching SCOTUS