Hi, Paul,

on Montag, 11. April 2005 at 21:15 you wrote to amanda-users:

PB> My current knowledge:

PB> 1.13.19 is good.  However it still sets return code 2 for some
PB>      infrequent conditions even with --ignore-failed-read option.
PB>      This results in amanda thinking the total archive is bad,
PB>      and drops the complete archive.  Those conditions are very rare
PB>      on a quiet filesystem.

PB> 1.13.25: no problems found (yet).

PB> 1.13.9x  have changed the format of "tar -t", resulting in amrecover
PB>      not able to use the indexes.

PB> 1.14.x writes good archives, but when restoring, it has trouble
PB>      with sparse files; the sparse file itself, and *all* files after it
PB>      cannot be read anymore.  But you can read the archive with a good
PB>      tar version (i.e. the tar images produced are fine).

PB> 1.15.1 no problems found (yet).   I'm using this version on most of
PB>      my clients since january this year, and have already done
PB>      successful restore too.

Thanks a lot, Paul, for this listing. At slashdot.org I would moderate
this as "Informative" ;-)

If anyone has had the same or different experiences, please let us
know. I'll include this information in the docs as soon as things
have cleared up.

-- 
best regards,
Stefan

Stefan G. Weichinger
mailto:monitor AT oops.co DOT at