Amanda-Users

amrecover error

2003-01-12 12:58:28
Subject: amrecover error
From: Gene Heskett <gene_heskett AT iolinc DOT net>
To: amanda-users AT amanda DOT org
Date: Sun, 12 Jan 2003 12:04:51 -0500
Its Gene and here I come asking for assistance for a change :(

While trying to install the latest wine, I ran out of space on 
/home.

So I fired up fr to do some space patrol since I had the last 20 or 
so release build directories in /home/amanda.  Removing a few of 
the older ones seemed like a good thing to do.  fr changed the name 
under the lightlight as it recovered from the previous operation so 
I wound up deleting the wrong directory tree, in this case it was 
/home/amanda/"amanda" which contained aanother dir "config-bak".

I figured no problem since I now have it setup to make several 
copies of the various amanda config and indexes by doing a seperate 
tar operation and making a rotating backup of those in some out of 
the way place like /home/amanda/amanda/config-bak.  So now its 
gone.

running amrecover, I go thru the setups and make a /tmp/amrestore 
dir giving amanda:disk as perms to write to it.
I add /home/amanda to the extract list and type extract, at which 
point the fun stops.
===================copied from shell============
[root@coyote amanda]# amrecover
AMRECOVER Version 2.4.3-20030104. Contacting server on 
coyote.coyote.den ...
220 coyote AMANDA index server (2.4.3-20030104) ready.
200 Access OK
Setting restore date to today (2003-01-12)
200 Working date set to 2003-01-12.
200 Config set to DailySet1.
501 Host coyote.coyote.den is not in your disklist.
Trying host coyote.coyote.den ...
501 Host coyote.coyote.den is not in your disklist.
Trying host coyote ...
200 Dump host set to coyote.
Trying disk /home ...
$CWD '/home/amanda' is on disk '/home' mounted at '/home'.
200 Disk set to /home.
/home/amanda
WARNING: not on root of selected filesystem, check man-page!
amrecover> list
amrecover> lcd /tmp/amrestore
amrecover> add amanda
Added dir /amanda/amanda at date 2003-01-12
Added dir /amanda/amanda at date 2003-01-10
amrecover> extract

Extracting files using tape drive 0 on host 192.168.1.3.
The following tapes are needed: DailySet1-28
                                DailySet1-02

Restoring files into directory /tmp/amrestore
Continue [?/Y/n]? y

Extracting files using tape drive 0 on host 192.168.1.3.
Load tape DailySet1-28 now
Continue [?/Y/n/s/t]? y
EOF, check amidxtaped.debug file on 192.168.1.3.
amrecover: short block 0 bytes
UNKNOWN file
amrecover: Can't read file header
extract_list - child returned non-zero status: 1
Continue [?/Y/n/r]?
==============================
Is there something I missed up to this point?
Here is that debug file
==============================
amidxtaped: debug 1 pid 8895 ruid 33 euid 33: start at Sun Jan 12 
11:40:20 2003
amidxtaped: version 2.4.3-20030104
amidxtaped: time 0.000: > SECURITY USER root
amidxtaped: time 0.000: bsd security: remote host coyote.coyote.den 
user root local user amanda
amidxtaped: time 0.000: amandahosts security check passed
amidxtaped: time 0.000: > CONFIG=DailySet1
amidxtaped: time 0.000: > LABEL=DailySet1-28
amidxtaped: time 0.000: > FSF=2
amidxtaped: time 0.000: > HEADER
amidxtaped: time 0.000: > DEVICE=0
amidxtaped: time 0.000: > HOST=^coyote$
amidxtaped: time 0.000: > DISK=^/home$
amidxtaped: time 0.000: > DATESTAMP=20030110
amidxtaped: time 0.000: > END
amidxtaped: time 0.002: amrestore_nargs=0
amidxtaped: time 0.002: Ready to execv amrestore with:
path = /usr/local/sbin/amrestore
argv[0] = "amrestore"
argv[1] = "-p"
argv[2] = "-h"
argv[3] = "-l"
argv[4] = "DailySet1-28"
argv[5] = "-f"
argv[6] = "2"
argv[7] = "0"
argv[8] = "^coyote$"
argv[9] = "^/home$"
argv[10] = "20030110"
amrestore: could not stat 0
amidxtaped: time 0.004: amrestore terminated normally with status: 2
amidxtaped: could not stat 0
amidxtaped: time 0.005: could not stat 0
amidxtaped: time 0.005: pid 8895 finish time Sun Jan 12 11:40:20 
2003
=============================
and the shell is still sitting there.  I've found I cannot rerun 
amrecover without first doing an amcleanup from the previous failed 
run, but thats been done before I re-invoked amrecover this time.

I have no idea whats missing from argv[7] or even what its supposed 
to be.

-- 
Cheers, Gene
AMD K6-III@500mhz 320M
Athlon1600XP@1400mhz  512M
99.22% setiathome rank, not too shabby for a WV hillbilly

<Prev in Thread] Current Thread [Next in Thread>