-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi! If one tries to append a file to an existing .tar file through
tar --append --file defective.tar fileToAdd.xxx tar may return exit code 0 and terminate without error though the fileToAdd.xxx is not added to the .tar file. However the tarfile has been changed in some kinde since md5sums of defective.tar befor the non working call and after the call differ. If the above command is issued a second time the file `fileToAdd.xxx` is correctly appendet to the defective.tar. (So defective.tar must have been `repaired` in some weird way) The expected result is either - the appending of fileToAdd.xxx to defective.tar _DID NOT_ work and tar returns with an error (exit code !=0) indicating fileToAdd.xxx could not be added .OR. - the appending of fileToAdd.xxx to defective.tar _DID_ work and tar exits with exit code 0 and fileToAdd.xxx is included into defective tar. The tar file I am experiencing this issue is generated by pg_basebackup, an official backup programm for Postgres Database. I issued a bug report there, too since their generated .tar file is somewhat defective. Since tar did not complain about this "defective" tar it is a bug within tar also. The defective tar file (generated by pg_basebackup) may be found here: https://depot.tu-dortmund.de/get/8aq4g If you need any further information feel free to contact me. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) iQEcBAEBAgAGBQJUY3ZgAAoJEM8IZdIKCW978csIAJ4ocH0yOyOOESuE1axoX1Me smcVUCG72JcqHCWrUq7h4Ju4IFS3NsNikyKuATFKntSl1B52rXosVvWoJtSsgZdP 6KUCbw0+z4Xtoj40C2w+8uTrP8BlFBiQWa8e+bUGo2G/sgOMqsTRakEWRAp55mSn vh2qDBvhFL24PxuoU49FifIkoiGFXJk9Mppv+TbPtM/b5b8ijrMlz8fkfbzA5CFo /1x7y0X/K+0+iP2YvAt0F0L/ZNqFU0xf9/Vcju0MUMAIbWSKNiy7y3M1MnTEqFPk EKIQEPpiHlruY+gF51LeBQGYD41q+j6nZ/dAeOGNiX6RM0bPEsPdN4slUdxvQFE= =pyyk -----END PGP SIGNATURE-----
