Re: 2.6.1alpha-20081121 oddity
On Monday 24 November 2008, Jean-Louis Martineau wrote: >What are you extracting? If the DLE have hard link you must extract the >complete DLE. gtar save the DLE only for the first file, this file must >be extracted. >You tried to extract './sysconfig/networking/profiles/default/hosts' but >you didn't extracted './hosts'. Because it had already been pulled, and added to. Spare box in the basement, now I can play with new linux releases. :) >Which release of amrecover are you using? See subject line, I'd just installed it. And I found out how to trigger a rescan, thanks to Tejun Heo, so I now have the source of those files mountable. I pulled a few more things from it, and now have an 'e2fsck -c -c /dev/sdd1' running on it to see if that will make it remap some badblocks. I think I'll warranty it anyway, 3 year drive, got less than a year out of it. Thanks for the explanation, and thank you. >Jean-Louis > >Gene Heskett wrote: >> Greetings; >> >> I have not restarted the nightly amanda run yet, still fine tuning this >> new install. >> >> amrecover finally decided to work for about 95% of the time, but I find >> its an exellent hard link finder, cuz tar can't deal with those and does >> an error exit: >> >> ./sysconfig/networking/profiles/default/hosts >> tar: ./sysconfig/networking/profiles/default/hosts: Cannot hard link to >> `./hosts': No such file or directory >> ./sysconfig/networking/profiles/default/ifcfg-eth0 >> ./sysconfig/networking/profiles/default/network >> ./sysconfig/networking/profiles/default/resolv.conf >> tar: ./sysconfig/networking/profiles/default/resolv.conf: Cannot hard link >> to `./resolv.conf': No such file or directory >> tar: Error exit delayed from previous errors >> Extractor child exited with status 2 >> Extracting files using tape drive chg-disk on host coyote. >> = >> this doesn't surprise me as I was extracting to /tmp, not /etc. But this >> next thing bothers me. Can it not get that -o info the >> /$config/amanda.conf? = >> Load tape Dailys-13 now >> Continue [?/Y/n/s/d]? >> warning: restore program for APPLICATION not available. >> amrecover couldn't exec: No such file or directory >> problem executing restore >> Extractor child exited with status 1 >> Extracting files using tape drive chg-disk on host coyote. >> Load tape Dailys-16 now >> Continue [?/Y/n/s/d]? >> warning: restore program for APPLICATION not available. >> amrecover couldn't exec: No such file or directory >> problem executing restore >> Extractor child exited with status 1 >> amrecover> exit >> 200 Good bye. >> >> I would assume I would set the '-o amgtar' option on the cli, in which >> case the first extraction above would probably have failed, while the last >> 2 tapes would have been read ok instead of the error. >> >> Comments Dustin? Have I uncovered a potential gotcha? These tapes >> straddle the time frame where I converted to using amgtar. -- 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) Mal: "Well, lady I must say..." (admiring smile) "...you're my kinda stupid." --Episode #13, "Heart of Gold"
sendbackup: broken pipe
Hello, every now and then I see this error on an otherwise perfectly working Amanda system (server 2.4.4p3, client 2.5.1p1): FAILURE AND STRANGE DUMP SUMMARY: host.staso / lev 0 FAILED [data timeout] The client's sendbackup log for such a failed run: sendbackup: debug 1 pid 14726 ruid 34 euid 34: start at Fri Nov 21 22:46:00 2008 sendbackup: version 2.5.1p1 Could not open conf file "/etc/amanda/amanda-client.conf": No such file or directory sendbackup req: parsed request as: program `GNUTAR' disk `/' device `/' level 0 since 1970:1:1:0:0:0 options `|;bsd-auth;no-record;index;exclude-list=.backup.exc;exclude-optional;' sendbackup: start: host.stasoft.ch:/ lev 0 sendbackup-gnutar: time 0.006: doing level 0 dump as listed-incremental to '/var/lib/amanda/gnutar-lists/host.stasoft.ch__0.new' sendbackup-gnutar: time 0.010: doing level 0 dump from date: 1970-01-01 0:00:00 GMT sendbackup: time 0.015: spawning /usr/lib/amanda/runtar in pipeline sendbackup: argument list: runtar NOCONFIG gtar --create --file - --directory / --one-file-system --listed-incremental /var/lib/amanda/gnutar-lists/host.stasoft.ch__0.new --sparse --ignore-failed-read --totals --exclude-from /tmp/amanda/sendbackup._.20081121224600.exclude . sendbackup: time 0.078: started index creator: "/bin/tar -tf - 2>/dev/null | sed -e 's/^\.//'" sendbackup-gnutar: time 0.082: /usr/lib/amanda/runtar: pid 14729 sendbackup: time 0.083: started backup sendbackup: time 2996.696: index tee cannot write [Broken pipe] sendbackup: time 2996.718: pid 14728 finish time Fri Nov 21 23:35:57 2008 sendbackup: time 2996.697: 118: strange(?): sendbackup: index tee cannot write [Broken pipe] sendbackup: time 2996.751: 118: strange(?): sed: couldn't flush stdout: Broken pipe sendbackup: time 2996.779: 47:size(|): Total bytes written: 16497745920 (16GiB, ?/s) sendbackup: time 2996.780: 118: strange(?): gtar: -: Wrote only 4096 of 10240 bytes sendbackup: time 2996.781: 118: strange(?): gtar: Error is not recoverable: exiting now sendbackup: time 2996.781: parsed backup messages sendbackup: time 2996.781: pid 14726 finish time Fri Nov 21 23:35:57 2008 On the server side, the amdump log contains: [...] driver: send-cmd time 2015.907 to dumper0: FILE-DUMP 01-00032 /amholdingdisk/20081121/host.stasoft.ch._.0 host.stasoft.ch feff9ffeff / NODEVICE 0 1970:1:1:0:0:0 1048576 GNUTAR 49498848 |;bsd-auth;no-record;index;exclude-list=.backup.exc;exclude-optional; [...] driver: result time 6812.702 from dumper0: FAILED 01-00032 [data timeout] [...] Hmm, but most of the time I do _not_ see this problem. Any hints what could cause the problem or how to debug this further? Regards, Jukka -- bashian roulette: $ ((RANDOM%6)) || rm -rf ~
Re: 2.6.1alpha-20081121 oddity
What are you extracting? If the DLE have hard link you must extract the complete DLE. gtar save the DLE only for the first file, this file must be extracted. You tried to extract './sysconfig/networking/profiles/default/hosts' but you didn't extracted './hosts'. Which release of amrecover are you using? Jean-Louis Gene Heskett wrote: Greetings; I have not restarted the nightly amanda run yet, still fine tuning this new install. amrecover finally decided to work for about 95% of the time, but I find its an exellent hard link finder, cuz tar can't deal with those and does an error exit: ./sysconfig/networking/profiles/default/hosts tar: ./sysconfig/networking/profiles/default/hosts: Cannot hard link to `./hosts': No such file or directory ./sysconfig/networking/profiles/default/ifcfg-eth0 ./sysconfig/networking/profiles/default/network ./sysconfig/networking/profiles/default/resolv.conf tar: ./sysconfig/networking/profiles/default/resolv.conf: Cannot hard link to `./resolv.conf': No such file or directory tar: Error exit delayed from previous errors Extractor child exited with status 2 Extracting files using tape drive chg-disk on host coyote. = this doesn't surprise me as I was extracting to /tmp, not /etc. But this next thing bothers me. Can it not get that -o info the /$config/amanda.conf? = Load tape Dailys-13 now Continue [?/Y/n/s/d]? warning: restore program for APPLICATION not available. amrecover couldn't exec: No such file or directory problem executing restore Extractor child exited with status 1 Extracting files using tape drive chg-disk on host coyote. Load tape Dailys-16 now Continue [?/Y/n/s/d]? warning: restore program for APPLICATION not available. amrecover couldn't exec: No such file or directory problem executing restore Extractor child exited with status 1 amrecover> exit 200 Good bye. I would assume I would set the '-o amgtar' option on the cli, in which case the first extraction above would probably have failed, while the last 2 tapes would have been read ok instead of the error. Comments Dustin? Have I uncovered a potential gotcha? These tapes straddle the time frame where I converted to using amgtar.
