Re: restore errors
Stefan G. Weichinger schrieb: Stefan G. Weichinger schrieb: googled a bit and found notes about a bug in 2.4.4, but I am unsure if I hit this particular one. Could anyone *please* let me know if this problem would be avoided with a more recent release of Amanda? So noone knows if there are releases out there that are known to archive defective tarballs? IMO it would be the least to mark these releases as buggy ones, to make clear which installations should upgrade to get valid restores again, and which installations would just need to upgrade for new features or something. But it seems that this interests noone but me. Stefan
Re: restore errors
On Saturday 27 January 2007 09:14, Stefan G. Weichinger wrote: Stefan G. Weichinger schrieb: Stefan G. Weichinger schrieb: googled a bit and found notes about a bug in 2.4.4, but I am unsure if I hit this particular one. Could anyone *please* let me know if this problem would be avoided with a more recent release of Amanda? So noone knows if there are releases out there that are known to archive defective tarballs? IMO it would be the least to mark these releases as buggy ones, to make clear which installations should upgrade to get valid restores again, and which installations would just need to upgrade for new features or something. But it seems that this interests noone but me. Stefan I believe that more of the blame for defective backups can be laid at the gnu.org's (miss)handling of tar than at amanda's doorstep. Amanda has always had the possibility that something would sneak in, and it did at least twice on my watch, but was fixed each time in good time, less than a week IIRC. Tar on the other hand, has caused us no end of headaches and I've often wondered if we would be better off using star. I think its probably very good code, but Jeorg Schiling(sp) is such a difficult person to deal with that the ever buggy tar is perceived as the better choice. -- Cheers, Gene There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order. -Ed Howdershelt (Author) Yahoo.com and AOL/TW attorneys please note, additions to the above message by Gene Heskett are: Copyright 2007 by Maurice Eugene Heskett, all rights reserved.
Re: restore errors
Gene Heskett schrieb: I believe that more of the blame for defective backups can be laid at the gnu.org's (miss)handling of tar than at amanda's doorstep. Amanda has always had the possibility that something would sneak in, and it did at least twice on my watch, but was fixed each time in good time, less than a week IIRC. I was under the impression for years now that tar 1.13.25 was known as a release that works well with Amanda. Nothing specific with that setup, plain Suse Linux, etc. I don't blame Amanda for anything, I just wonder if anyone else has hit that bug I seem to have hit, and which patch/release fixed that issue (if it has been fixed already). Is that issue known? Is it documented? Is it fixed already? Jean-Louis, maybe you know best ... IMO this is an issue that should be communicated and discussed, regardless where the bug comes from. Tar on the other hand, has caused us no end of headaches and I've often wondered if we would be better off using star. I think its probably very good code, but Jeorg Schiling(sp) is such a difficult person to deal with that the ever buggy tar is perceived as the better choice. Agreed. Stefan
Re: restore errors
On Saturday 27 January 2007 13:15, Stefan G. Weichinger wrote: Gene Heskett schrieb: I believe that more of the blame for defective backups can be laid at the gnu.org's (miss)handling of tar than at amanda's doorstep. Amanda has always had the possibility that something would sneak in, and it did at least twice on my watch, but was fixed each time in good time, less than a week IIRC. I was under the impression for years now that tar 1.13.25 was known as a release that works well with Amanda. Nothing specific with that setup, plain Suse Linux, etc. It does, but that's not the release that now comes with the various distros. 1.15-1 also works well, if built from the tarball, but some distros have backported 1.16 things and their package is then broken for amanda's use according to old messages here. I don't blame Amanda for anything, I just wonder if anyone else has hit that bug I seem to have hit, and which patch/release fixed that issue (if it has been fixed already). I don't recall seeing the version you were fighting with posted, did I miss it? ISTR I had a 2 day problem about 90 days ago. But don't recall the greasy details now. The recent ChangeLog might have some clues. Is that issue known? Is it documented? Is it fixed already? Jean-Louis, maybe you know best ... IMO this is an issue that should be communicated and discussed, regardless where the bug comes from. Tar on the other hand, has caused us no end of headaches and I've often wondered if we would be better off using star. I think its probably very good code, but Jeorg Schiling(sp) is such a difficult person to deal with that the ever buggy tar is perceived as the better choice. Agreed. Yes, but that still doesn't make Jeorg the least bit palatable. As an official old fart, I can be difficult, but I can't even hold the candle to light his way. Stefan -- Cheers, Gene There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order. -Ed Howdershelt (Author) Yahoo.com and AOL/TW attorneys please note, additions to the above message by Gene Heskett are: Copyright 2007 by Maurice Eugene Heskett, all rights reserved.
Re: restore errors
Stefan G. Weichinger schrieb: googled a bit and found notes about a bug in 2.4.4, but I am unsure if I hit this particular one. Could anyone *please* let me know if this problem would be avoided with a more recent release of Amanda? Thank you, Stefan.
restore errors
Greets, amanda-users, received a call from a customer today, there are problems with restoring files on a Amanda-2.4.4p3-machine. amrecover crashed so I went in to do: # amrestore /dev/nst0 serverX /usr/daten/DATEN amrestore: 0: skipping start of tape: date 20070118 label daily15 amrestore: 1: skipping serverX._boot.20070118.0 amrestore: 2: skipping serverX._var.20070118.0 amrestore: 3: skipping serverX._.20070118.0 amrestore: 4: restoring serverX._usr_daten_DATEN.20070118.0 gzip: stdin: invalid compressed data--format violated Error 32 (Broken pipe) offset 18055168+32768, wrote 0 amrestore: pipe reader has quit in middle of file. --- Bad ... An amrestore -r worked out fine, so it seems the file's content itself is corrupt. I get these errors with two different tapes, so the problem seems to be the compression of that DLE. Another DLE (/var) restores fine which seems to point out that not the hardware/tape is the problem. googled a bit and found notes about a bug in 2.4.4, but I am unsure if I hit this particular one. Any help in sight? I should restore 100MB of files from this DLE if possible. I have the raw DLE-restore on disk now, I try to list content: # dd if=serverX._usr_daten_DATEN.20070118.0 bs=32k skip=1 | /bin/tar -tzf - and it hangs with /bin/tar: Skipping to next header gzip: stdin: invalid compressed data--format violated /bin/tar: Child died with signal 13 /bin/tar: Error exit delayed from previous errors 552+0 records in 551+0 records out after displaying a few dozens of lines ... Thanks, greets, Stefan.
