As said, I changed to tar 1.27 and now the problem has disappeared. I
cleaned all what was necessary and started with a full backup on all
DLEs. There was some strange tar message on the single dle at the
external client stremen ("... /usr/local/bin/tar exited with status
2 .."), but as this was a dle which worked normally also with the
previous version of tar on stremen, I decided to revert that
single dumptype to not using /usr/local/bin/tar (1.27).
I forced all fiume (the server/client) dle to level 1 and did a
subsequent amdump. All worked fine, and the single stremen dle was
also ok on level 0.
Then I forced everything to level 1, including stremen and did a 3rd
amdump. Everything OK! The small problem with 1.27 tar on stremen will
have to wait. I checked a file with stat at various stages, but the
times are not affected by tar 1.27 at all, they don't change a bit.
Because tar 1.26 worked without problems in my previous suse 11.4 with
kernel 2.6.37, but does not want to work with my current suse 13.1 with
3.11.10 kernel, I suppose there is some incompatibility between them.
I keep my fingers crossed. Again many thanks for the assistance.
Regards, Charles
On Tue, 25 Feb 2014 17:48:13 +0100
Charles Stroom <char...@stremen.xs4all.nl> wrote:
> Jean-Louis,
>
> It's getting complicated, because in my previous post below I reported
> that with option "--atime-preserve=system" a level 1 tar incremental
> worked. However, some time later it didn't work any more, so it is
> really "unpredictable".
>
> I have repeated part of below with some stat in between. Results are
> in attachment tar_1.26_incremental. It seems that in the first
> create tar changes atime.
>
> Because I got no good results so far, I have installed the latest 1.27
> tar from gnu, which is in /usr/local/bin and repeated the results from
> above. With 1.27 no times are changed at level 0 or level 1. Results
> in attachment tar_1.27_incremental.
>
> Both tests actually did (now) a proper incremental tar as can be seen
> from the the size of the created files:
> -rw-r--r-- 1 charles users 379238400 Feb 25 17:23 wine_docs_0.tar
> -rw-r--r-- 1 charles users 71680 Feb 25 17:24 wine_docs_1.tar
> -rw-r--r-- 1 charles users 13405 Feb 25 17:24 wine_docs.snar
> -rw-r--r-- 1 charles users 1785 Feb 25 17:28
> tar_1.26_incremental -rw-r--r-- 1 charles users 379238400 Feb 25
> 17:36 wine_docs_0_1.27.tar -rw-r--r-- 1 charles users 71680 Feb
> 25 17:36 wine_docs_1_1.27.tar -rw-r--r-- 1 charles users 13405
> Feb 25 17:36 wine_docs_1.27.snar -rw-r--r-- 1 charles users
> 2100 Feb 25 17:39 tar_1.27_incremental
>
>
> I am now continuing with amanda, but testing takes much longer. But
> my best bet now is to use 1.27 and I will use amgtar to do achieve
> that.
>
> Regards, Charles
>
>
>
--
Charles Stroom
email: charles at no-spam.stremen.xs4all.nl (remove the "no-spam.")
