"Alford, Seth" <[email protected]> wrote: > I suspected that the problem might only occur when the backups > and files were larger. So, I rewrote test_multiple_volumes to > take parameters. Among the parameters it accepts are the number > of loopback disks, the size of the loopback disks, the size of > the files to back up, the files that the script should try to > delete, whether the script should re-run the test, and whether > the script should re-create the test files for the 2nd and > subsequent runs.
When I first identified that GNU tar has problems with multi volume archives in 2004, it turned out that the problem was caused by the exact position of the volume break. For my cases, GNU tar did try to verify whether the next volume is a cotinuation volume using parameters from the archives that are not reliable. Star for this reason uses a different method to verify whether a valid continuation volume is present with the star multi volume system. Star does not create GNU tar multi volume archives and does not try to verify whether a volume is a valid GNU tar multivolume continuation when star reads GNU tar multi volume archives. If you are able to read back your archives using star, then you suffer from the same problem as I did in 2004. Jörg -- EMail:[email protected] (home) Jörg Schilling D-13353 Berlin [email protected] (uni) [email protected] (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily
