tar version 1.14 not good !
Just had my first bad experience with gnutar 1.14. It seems there is a bug when restoring archives with sparse files. When restoring with gnutar 1.14, you cannot restore a sparse file and ALL OTHER FILES AFTER THAT MEMBER. From my extraction: Load tape DAILY-18 now Continue [?/Y/n/s/t]? y tar: ./XXX/XXX.mdb: invalid sparse archive member tar: Skipping to next header tar: Archive contains obsolescent base-64 headers The archive itself is fine, because restoring with good old tar 1.13.25 did work fine. There is already a patched version 1.14.91 from alpha.gnu.org: http://lists.gnu.org/archive/html/bug-tar/2004-12/msg00014.html . Downgrading to 1.13.25 works too (at least in my case). A warned man... -- Paul Bijnens, XplanationTel +32 16 397.511 Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512 http://www.xplanation.com/ email: [EMAIL PROTECTED] *** * I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, F6, * * quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, * * stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, * * PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, * * kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ...* * ... Are you sure? ... YES ... Phew ... I'm out * ***
calc size question
Is there any documentation on how to implement the use of the calc or server options for estimates in 2.5? I don't see anything in the examples. -- George Kelbley System Support Group Computer Science Department University of New Mexico 505-277-6502 Fax: 505-277-6927
Re: calc size question
On Mon, Dec 20, 2004 at 10:51:50AM -0700, George Kelbley wrote: Is there any documentation on how to implement the use of the calc or server options for estimates in 2.5? I don't see anything in the examples. man amanda -- George KelbleySystem Support Group Computer Science Department University of New Mexico 505-277-6502 Fax: 505-277-6927 -- Jean-Louis Martineau email: [EMAIL PROTECTED] Département IRO, Université de Montréal C.P. 6128, Succ. CENTRE-VILLETel: (514) 343-6111 ext. 3529 Montréal, Canada, H3C 3J7Fax: (514) 343-5834
Re: sendbackup failure
--On Monday, December 20, 2004 09:37:42 -0800 Narada Hess [EMAIL PROTECTED] wrote: Hi, I'm not sure whether this reached the list, as I have gotten no responses. So I'll try again. I have been searching the net for info related to the below without any definitive success. Thanks in advance for any help... I am having some problems with a backup that used to run fine. The client and server are the same machine, running RedHat 8.0, with Amanda version 2.4.5b1. Anyone have any ideas? Two problems: 1. Amanda seems to think the dump is larger than the tape, even though after taking the exclude files into account, the total to be dumped is about 90 Gb onto a tape I have defined in amanda.conf to be 200 Gb capacity. Is it possible that the exclude file is being ignored or improperly processed? It is shown in the gtar command in the /tmp/amanda logs and looks fine. 2. We get this error in /tmp/amanda. Since our client and server are the same machine (no NFS or anything), and since this used to work just fine before we added about 100Gb to the filesystem to be backed up, I suspected that the large amount of very compressible data might be causing a timeout. But then we see the exact same results even after adding the offending directory to the exclude file. sendbackup: time 3119.004: index tee cannot write [Broken pipe] Exclude file: ./archive ./externals ./products ./Sustaining_Eng Amanda Report: FAILED AND STRANGE DUMP DETAILS: /-- mysystem /scd lev 8 FAILED [data timeout] Have you tried increasing dtimeout (its a different variable than etimeout)? sendbackup: start [mysystem:/scd level 8] sendbackup: info BACKUP=/bin/gtar sendbackup: info RECOVER_CMD=/bin/gtar -f... - sendbackup: info end \ NOTES: planner: mysystem /scd 20041215 0 [dump larger than tape, 291395220 KB, full dump delayed] Amanda thinks that a level 0 of this will take 291 GB, which is larger than your tape. Are you using hardware or software compression? If hw, then Amanda doesn't know how much room it will take on tape, you might need to set the 'comprate' variable in your dumptype. Frank planner: Full dump of mysystem:/ promoted from 6 days ahead. planner: Full dump of mysystem:hda1 promoted from 6 days ahead. taper: tape DailySet1-002 kb 4595040 fm 3 [OK] DUMP SUMMARY: DUMPER STATS TAPER STATS HOSTNAME DISK L ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS KB/s --- --- --- mysystem / 0 4573540 4573540 -- 17:22 4387.4 17:23 4386.6 mysystem /scd 8 FAILED mysystem hda1 0 21350 21350 -- 0:02 11883.4 0:02 11181.6 (brought to you by Amanda version 2.4.5b1) Narada Hess Advanced Digital Information Corporation 3170 Coronado Drive, Santa Clara, CA 95054 408 350-1409 -- Frank Smith [EMAIL PROTECTED] Sr. Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
