Re: Amanda error Unexpected field value...
On Tue, 17 Oct 2006, Paul Yeatman wrote:
Just to follow up on this, I was forced to downgrade to tar version
1.15.1 before things worked correctly and without the Unexpected field
value messages. Things were just not working as expected with 1.15.91.
Indeed.
JFYI, Debian recently released an update of 1.15.91 (1.15.91-2.1), which fixes
some bugs w.r.t. restores of incrementals.
But the issue with creating incrementals and escaping to different file systems
is still there :-(
-In response to your message-
--received from Paul Yeatman--
I have run into the exact same problem on a client that is running
Debian (Etch) linux using tar version 1.15.91 (and amanda 2.5.0p2-1).
I have now noticed, given your message, that things worked fine with
the first Debian tar 1.15.91 package but, when a revised tar 1.15.91
package was released end of July, 2 of the 3 partitions on the client
began failing during the size estimation stage with the same tar
error message, Unexpected field value.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- [EMAIL PROTECTED]
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say programmer or something like that.
-- Linus Torvalds
amanda 2.5.1 doesn't compile on FreeBSD 4.11 - atoll
(Not sure if my messages are reaching the list so apologies if you're received this twice) I've been attempting to compile amanda 2.5.1 on FreeBSD 4.11 but run into this error on the make: amandad.c:826: warning: zero-length format string amandad.c:882: warning: zero-length format string amandad.c: In function `s_processrep': amandad.c:937: warning: zero-length format string /bin/sh ../libtool --tag=CC --mode=link gcc -Wall -W -Wparentheses -Wmissing-prototypes -Wstrict-prototypes -Wmissing-declarations -Wformat -Wsign-compare -D_GNU_SOURCE -L/usr/lib -o amandad amandad.o ../common-src/libamanda.la libamandad.la ../common-src/libamanda.la -lm -lreadline -ltermcap -lcam gcc -Wall -W -Wparentheses -Wmissing-prototypes -Wstrict-prototypes -Wmissing-declarations -Wformat -Wsign-compare -D_GNU_SOURCE -o .libs/amandad amandad.o -L/usr/lib ./.libs/libamandad.so ../common-src/.libs/libamanda.so -lm -lreadline -ltermcap -lcam -Wl,--rpath -Wl,/usr/local/amanda25/lib ../common-src/.libs/libamanda.so: undefined reference to `atoll' *** Error code 1 Stop in /usr/local/src/amanda-2.5.1/amandad-src. *** Error code 1 Stop in /usr/local/src/amanda-2.5.1. I've found references to this error on mailing lists but so far no solutions. Any suggestions? Oscar
Re: amanda 2.5.1 doesn't compile on FreeBSD 4.11 - atoll
Error: .libs/amandad amandad.o ./.libs/libamandad.so ../common-src/.libs/libamanda.so -lm -lreadline -ltermcap -lcam ../common-src/.libs/libamanda.so: undefined reference to `atoll' *** Error code 1 Stop in /usr/local/src/amanda/amandad-src. *** Error code 1 Solution: 1.Edit ./common-src/amanda.h file and modify this line: Old line: # define OFF_T_ATOI (off_t)atoll New line: # define OFF_T_ATOI (off_t)atol 2. run autogen 3. run configure 4. run make (Not sure if my messages are reaching the list so apologies if you're received this twice) I've been attempting to compile amanda 2.5.1 on FreeBSD 4.11 but run into this error on the make: amandad.c:826: warning: zero-length format string amandad.c:882: warning: zero-length format string amandad.c: In function `s_processrep': amandad.c:937: warning: zero-length format string /bin/sh ../libtool --tag=CC --mode=link gcc -Wall -W -Wparentheses -Wmissing-prototypes -Wstrict-prototypes -Wmissing-declarations -Wformat -Wsign-compare -D_GNU_SOURCE -L/usr/lib -o amandad amandad.o ../common-src/libamanda.la libamandad.la ../common-src/libamanda.la -lm -lreadline -ltermcap -lcam gcc -Wall -W -Wparentheses -Wmissing-prototypes -Wstrict-prototypes -Wmissing-declarations -Wformat -Wsign-compare -D_GNU_SOURCE -o .libs/amandad amandad.o -L/usr/lib ./.libs/libamandad.so ../common-src/.libs/libamanda.so -lm -lreadline -ltermcap -lcam -Wl,--rpath -Wl,/usr/local/amanda25/lib ../common-src/.libs/libamanda.so: undefined reference to `atoll' *** Error code 1 Stop in /usr/local/src/amanda-2.5.1/amandad-src. *** Error code 1 Stop in /usr/local/src/amanda-2.5.1. I've found references to this error on mailing lists but so far no solutions. Any suggestions? Oscar
Looooooooong backup
I have a monthly (full) backup running for about 22 hrs now. Do you think there is a problem, or is it possible it's just taking a long time? about 150G of data. Steve
Re: Looooooooong backup
Steven Settlemyre wrote: I have a monthly (full) backup running for about 22 hrs now. Do you think there is a problem, or is it possible it's just taking a long time? about 150G of data. Steve It depends on the speed of your network, disks, tape drive, and how busy the servers involved are with other things, but I would say it probably shouldn't take that long. What does amstatus say? Frank -- Frank Smith [EMAIL PROTECTED] Sr. Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
RE: tape order
This is what I do to keep my tapes in sequence. Say I have the following tape list. 20061010200953 D00025 reuse 20061009201023 D00024 reuse 0 D00023 reuse 20061009141704 D00022 reuse 20061008200944 D00021 reuse I change the time for D00023 to something in between D00022 and D00024. Such as 20061010200953 D00025 reuse 20061009201023 D00024 reuse 20061009141904 D00023 reuse 20061009141704 D00022 reuse 20061008200944 D00021 reuse I have several L0 dumps so for me this is not a problem. It is best to do this as time gets closer to the date you want to change to. To keep things in order I always run sort -r oldtapelist new tapelist The output will be sorted as above. The next tape on my list is always the bottom tape. Since I have been running amanda (3 years) my daily tapes have always been in sequence. Now my amadmin config tape list the correct tapes that will be used next. There is no rocket science in what I am doing but it works for me. Robert _ Robert P. McGraw, Jr. Manager, Computer System EMAIL: [EMAIL PROTECTED] Purdue University ROOM: MATH-807 Department of MathematicsPHONE: (765) 494-6055 150 N. University Street FAX: (419) 821-0540 West Lafayette, IN 47907-2067 -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Steve Wray Sent: Tuesday, October 17, 2006 4:03 PM To: amanda-users@amanda.org Subject: Re: tape order Jon LaBadie wrote: On Tue, Oct 17, 2006 at 11:44:53AM -0400, Steven Settlemyre wrote: I have 24 tapes and a 8 tape changer. For some reason, it is going 13-16-15-14-17. How can I fix this? can i just force it to take 14 after 13 by only having 14 in there when it's expecting 16? My tapecycle is 10. As Michael suggests, your human ordering is VERY likely to get out of sequence. Best to forget about it. This has been bugging me for years. It makes daily off-site storage of backup tapes problematic; the data-vault outfits typically need to know 24 hours in advance which tape they should bring to your site as they need to plan the route for their van. If you request that they send you a tape at 'short notice' they will typically charge extra for this. I've been looking for a way to get amanda to try to predict which tape it will want next in good time (a schedule for the next 3 days or so would be ideal). No luck so far... smime.p7s Description: S/MIME cryptographic signature
Re: Looooooooong backup
On Wed, Oct 18, 2006 at 01:14:57PM -0400, Steven Settlemyre wrote: I have a monthly (full) backup running for about 22 hrs now. Do you think there is a problem, or is it possible it's just taking a long time? about 150G of data. Have you tried a few amstatus cmds to see if it is still progressing? -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: Looooooooong backup
looks ok, but i'm not too experienced reading these See attached. Jon LaBadie wrote: On Wed, Oct 18, 2006 at 01:14:57PM -0400, Steven Settlemyre wrote: I have a monthly (full) backup running for about 22 hrs now. Do you think there is a problem, or is it possible it's just taking a long time? about 150G of data. Have you tried a few amstatus cmds to see if it is still progressing? HOSTNAME:/1 210k finished (13:43:44) HOSTNAME:/files2 1 163k finished (13:43:32) HOSTNAME:/files3 1 2069k finished (13:44:05) HOSTNAME:/usr 0 633514k finished (13:58:13) HOSTNAME:/usr/local 1 343k finished (13:43:22) HOSTNAME:/var 1 607265k finished (13:55:33) HOSTNAME:/029748k finished (16:11:36) HOSTNAME:/files1 0 8356982k finished (16:11:24) HOSTNAME:/usr 12k finished (16:11:39) HOSTNAME:/usr/local 16k finished (16:11:38) HOSTNAME:/1 43k finished (14:01:35) HOSTNAME:/files1 1 388k finished (14:01:30) HOSTNAME:/usr 1 8231k finished (14:01:26) HOSTNAME:/var 0 902479k finished (13:52:48) HOSTNAME:/1 130k finished (13:43:34) HOSTNAME:/usr 1 581k finished (13:43:47) HOSTNAME:/usr/local 1 143k finished (13:43:23) HOSTNAME:/0 no estimate HOSTNAME:/hd/vol_mnt0/shares/BioInf 0 16717144k dumping to tape (12:49:32) HOSTNAME:/hd/vol_mnt0/shares/MID 1 48k finished (13:45:28) HOSTNAME:/hd/vol_mnt0/shares/MolGene 01k finished (14:01:39) HOSTNAME:/hd/vol_mnt0/shares/NeuroGen 18k finished (13:43:21) HOSTNAME:/hd/vol_mnt0/shares/TermLab 0 19943829k finished (7:59:15) HOSTNAME:/hd/vol_mnt0/shares/admin01k finished (13:45:25) HOSTNAME:/hd/vol_mnt0/shares/bcl 0 11817155k finished (17:22:57) HOSTNAME:/hd/vol_mnt0/shares/biochem 1 13k finished (13:44:01) HOSTNAME:/hd/vol_mnt0/shares/confocal 01k finished (13:44:56) HOSTNAME:/hd/vol_mnt0/shares/histo01k finished (13:46:13) HOSTNAME:/hd/vol_mnt0/shares/immuno 1 44k finished (13:43:28) HOSTNAME:/hd/vol_mnt0/shares/mcard01k finished (13:46:10) HOSTNAME:/hd/vol_mnt0/shares/mysql01k finished (13:44:53) HOSTNAME:/hd/vol_mnt0/shares/neurosci 1 7331k finished (13:44:43) HOSTNAME:/hd/vol_mnt0/shares/surgery 11k finished (13:43:43) HOSTNAME:/hd/vol_mnt0/shares/sysadmin 0 1990k finished (14:01:28) HOSTNAME:/hd/vol_mnt0/shares/urology 123734k finished (13:46:08) HOSTNAME:/1 13k finished (14:01:36) HOSTNAME:/files1 0 9512632k finished (19:40:32) HOSTNAME:/files3 1 565385k finished (14:01:07) HOSTNAME:/files4 17k finished (14:01:37) HOSTNAME:/files5 0 19194467k finished (12:49:32) HOSTNAME:/files6 0 42482791k finished (6:09:01) HOSTNAME:/usr 11k finished (14:01:40) HOSTNAME:/usr/local 184929k finished (14:01:23) HOSTNAME:/1 15k finished (14:21:23) HOSTNAME:/files1 18k finished (14:21:24) HOSTNAME:/files2 1 278233k finished (14:32:04) HOSTNAME:/usr 11k finished (14:21:25) HOSTNAME:/usr/local 120995k finished (14:21:21) HOSTNAME:/var 167529k finished (14:21:02) HOSTNAME:/var/log 067191k finished (14:21:17) HOSTNAME:/var/mail1 1325234k finished (14:20:46) SUMMARY part real estimated size size partition : 51 estimated : 50125731490k flush : 0 0k failed : 10k ( 0.00%) wait for dumping: 00k ( 0.00%) dumping to tape : 1 16717144k ( 13.30%) dumping : 0 0k 0k ( 0.00%) ( 0.00%) dumped : 50 132653031k 125731490k (105.51%) (105.51%) wait for writing: 0 0k 0k ( 0.00%) ( 0.00%) wait to flush : 0 0k 0k (100.00%) ( 0.00%) writing to tape : 0 0k 0k ( 0.00%) ( 0.00%) failed to tape : 0 0k 0k ( 0.00%) ( 0.00%) taped : 49 115935887k 109014346k (106.35%) (
Re: Looooooooong backup
Sometimes on my FreeBSD box 'amstatus' output doesn't change during really long dumps. I've found the best way to find out if it's still running is to use the 'ps' command and grep for the phrase 'done' ie: 'ps -ax | grep done' Dump does a good job of reporting back how far it thinks it is in the process. ie:78% done -S
Re: Looooooooong backup
Thanks for all the responses. It finished about 10 mins after I sent the last message, but it did run out of tape(s)... But that's another issue. Steffan Vigano wrote: Sometimes on my FreeBSD box 'amstatus' output doesn't change during really long dumps. I've found the best way to find out if it's still running is to use the 'ps' command and grep for the phrase 'done' ie: 'ps -ax | grep done' Dump does a good job of reporting back how far it thinks it is in the process. ie:78% done -S
Re: Looooooooong backup
On Wed, Oct 18, 2006 at 01:14:57PM -0400, Steven Settlemyre wrote: I have a monthly (full) backup running for about 22 hrs now. Do you think there is a problem, or is it possible it's just taking a long time? about 150G of data. Is it closer to 150G in on file or 150G in one million files? As the number of files increases, the time it takes to do dumps/restores becomes dominated by the amount of time it takes to deal with individual files. Millions of files add up to extremely long dumps... -- Ross Vandegrift [EMAIL PROTECTED] The good Christian should beware of mathematicians, and all those who make empty prophecies. The danger already exists that the mathematicians have made a covenant with the devil to darken the spirit and to confine man in the bonds of Hell. --St. Augustine, De Genesi ad Litteram, Book II, xviii, 37
Infinite loop - still looping...
Amanda Tape Server Host Check - Holding disk /data/amanda: 185 GB disk space available, that's plenty slot 1: read label `B001', date `X' NOTE: skipping tape-writable test Tape B001 label ok NOTE: host info dir /etc/amanda/DailySet1/curinfo/hostname0 does not exist NOTE: it will be created on the next run. NOTE: index dir /etc/amanda/DailySet1/index/hostname0 does not exist NOTE: it will be created on the next run. NOTE: host info dir /etc/amanda/DailySet1/curinfo/hostname1 does not exist NOTE: it will be created on the next run. NOTE: index dir /etc/amanda/DailySet1/index/hostname1 does not exist NOTE: it will be created on the next run. NOTE: host info dir /etc/amanda/DailySet1/curinfo/hostname2 does not exist NOTE: it will be created on the next run. NOTE: index dir /etc/amanda/DailySet1/index/hostname2 does not exist NOTE: it will be created on the next run. Server check took 17.575 seconds Amanda Backup Client Hosts Check ERROR: hostname1: [can not read/write /etc/amandates: Permission denied] ERROR: hostname0: [can not read/write /etc/amandates: Permission denied] WARNING: hostname2: selfcheck request failed: timeout waiting for ACK Client check: 12 hosts checked in 29.827 seconds, 3 problems found (brought to you by Amanda 2.5.1) I've checked permissions, xinetd configs, firewall, and SELinux settings; all appear to be correct. -- Brad Willson, Sr. Computer Specialist UW GeneTests, UW Box: 358735 EM: [EMAIL PROTECTED] W: 206.221.4674, C: 425.891.2732 http://www.genetests.org
Re: Infinite loop - still looping...
is /etc directory permission similar to the following: drwxr-xr-x 85 root root 12288 Oct 17 12:13 /etc Please list the content of /etc/xinetd.d/amanda* file? Need to make sure the service is started by amandabackup --Kevin Brad Willson wrote: Amanda Tape Server Host Check - Holding disk /data/amanda: 185 GB disk space available, that's plenty slot 1: read label `B001', date `X' NOTE: skipping tape-writable test Tape B001 label ok NOTE: host info dir /etc/amanda/DailySet1/curinfo/hostname0 does not exist NOTE: it will be created on the next run. NOTE: index dir /etc/amanda/DailySet1/index/hostname0 does not exist NOTE: it will be created on the next run. NOTE: host info dir /etc/amanda/DailySet1/curinfo/hostname1 does not exist NOTE: it will be created on the next run. NOTE: index dir /etc/amanda/DailySet1/index/hostname1 does not exist NOTE: it will be created on the next run. NOTE: host info dir /etc/amanda/DailySet1/curinfo/hostname2 does not exist NOTE: it will be created on the next run. NOTE: index dir /etc/amanda/DailySet1/index/hostname2 does not exist NOTE: it will be created on the next run. Server check took 17.575 seconds Amanda Backup Client Hosts Check ERROR: hostname1: [can not read/write /etc/amandates: Permission denied] ERROR: hostname0: [can not read/write /etc/amandates: Permission denied] WARNING: hostname2: selfcheck request failed: timeout waiting for ACK Client check: 12 hosts checked in 29.827 seconds, 3 problems found (brought to you by Amanda 2.5.1) I've checked permissions, xinetd configs, firewall, and SELinux settings; all appear to be correct. -- Thank you! Kevin Till Amanda documentation: http://wiki.zmanda.com Amanda forums:http://forums.zmanda.com
