On Sun, May 20, 2012 at 00:20:10 +0300, Toomas Aas wrote: > Jean-Louis wrote: > > >It might be a feature/bug with level 1 backup, try a full of /storage. > > I did, and the dump of /storage did not include files under > /storage/lists. So it *might* be a bug with level 1 backup, but in > that case it's strange that it has never affected backup of /, as > indicated by Nathan above.
I did experimentation using a simple directory tree to emulate your move-to-new-partition situation, and confirmed that even in tar 1.26 (i.e. the current latest release) there's a bug that shows up in your particular situation. The conditions required to trigger the bug are pretty specific, though: you have to have a listed-incremental snapshot file that mentions files which were included in an earlier backup, and those *same archive member paths* have to be found in the current run, but now be found on separate partition. (So in other words the bug only triggers when you move files to a new partition but then mount that new partition back on top of the path where the files used to be found, and only when you do that between levels of an incremental backup. That's why normal backups of e.g. / are not affected, even though they do have other filesystems mounted under them -- and why your problem when away once you did a new level-0 backup of /storage.) Anyway, I posted a report of the bug to the bug-tar list: http://lists.gnu.org/archive/html/bug-tar/2012-05/msg00022.html , and will report back here to amanda-users if anything interesting comes out of the discussion there. Nathan ---------------------------------------------------------------------------- Nathan Stratton Treadway - [email protected] - Mid-Atlantic region Ray Ontko & Co. - Software consulting services - http://www.ontko.com/ GPG Key: http://www.ontko.com/~nathanst/gpg_key.txt ID: 1023D/ECFB6239 Key fingerprint = 6AD8 485E 20B9 5C71 231C 0C32 15F3 ADCD ECFB 6239
