>amrestore: short file header block: 26624 bytes
What do you get if you do this:
mt -f /dev/tape rewind
dd if=/dev/tape bs=32k count=1 > /tmp/f0.b0
ls -l /tmp/f0.b0
strings /tmp/f0.b0
>amrestore: WARNING: not at start of tape, file numbers will be offset
Had you positioned this tape wi
>I'd be prepared to have a shot at implementing it, if my patches have some
>chance of being accepted. :-)
I'm sure they would. However, I'd strongly recommend you start with the
main development branch (the main trunk, w/o any -r option), as it has
a new security model that is supposed to make
On Tue, 23 Jan 2001, Ben Hyatt wrote:
>
>amcheck returns the following on my tape server host (atsun01) e450 2.7
>solaris:
>
>(*insecure*)amanda@atsun01:/usr/local/etc/amanda/atlab$ amcheck atlab
>Amanda Tape Server Host Check
>-
I could be smoking something here, but
>Is it possible that the error message could be improved?
Sure. Do you have a suggestion?
For starters, it should state that the error is coming from the client, not
from amcheck on the tape server. Something like:
"Client-side error: unable to perform reverse lookup on ".
Ben
I am having a problem reading the tapes written by Amanda. This is a
new install using a Seagate Travan IDE drive. Amdump seems to run fine
and there is definitely data written to tape as I can read chunks back
with 'mt fsf' and 'cp /dev/tape whatever'. However both amverify and
amrecover r
I see that it's possible to encrypt client/server traffic with Kerberos 4.
Might it be possible to implement a simpler, less onerous security scheme
such as the private key CAST-128 algorithm?
I'd be prepared to have a shot at implementing it, if my patches have some
chance of being accepted. :-)
>I don't have a tape changer defined (I found that when I used chg-manual, I
>had to be present to run amcheck!). ...
If you look at the chg-manual script, it has comments that describe how
you can make it work unattended.
>What will happen if I overflow a tape
>without a changer defined? Will
I don't have a tape changer defined (I found that when I used chg-manual, I
had to be present to run amcheck!). What will happen if I overflow a tape
without a changer defined? Will the backup fail?
Thanks, Ben
jrj wrote:
The only things I can think of to try at this point are a complete
rebuild of Amanda (blow away all traces of the build area you used
before), or upgrading to the latest gcc and building that for the
specific host, or making sure you have all the latest Solaris patches.
Yo
>Is it possible that the error message could be improved?
Sure. Do you have a suggestion?
I'm not sure what 2.5 will say about this. The new security framework
has significantly altered the flow in this area.
>Ben
John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
It says that when Amanda tried to do a reverse lookup (IP
203.24.38.228 back to a host name), it failed.
Ahh. Problem sorted, thanks. Name service had died at that machine's site.
Is it possible that the error message could be improved?
Being able to ping the host is irrelevant. I as
I have just brought a raidzone 1 TB box online.
Seems faster than our old netapp, and for 20,000 $ -
Joshua E Warchol wrote:
>
> Has anyone successfully backed up larger reiserfs partitions? One of my co-
> workers has setup a new Linux workstation with reiserfs for everything but
> /boot
>ERROR: metro: [addr 203.24.38.228: hostname lookup failed]
FYI, this is reported from the client side, so you need to do your
testing there, not on the server.
>This is nonsense -- I can ping the host, so my resolver is not broken.
>What else can cause this?
It says that when Amanda tried to d
> I don't think this would matter, but what do you get when you run
> "gcc -v"? Was it built for the OS version you have (2.7, as I recall)?
atsun01:/# gcc -v
Reading specs from /usr/local/lib/gcc-lib/sparc-sun-solaris2.7/2.8.1/specs
gcc version 2.8.1
I might add that this was a package, courte
I just got a note from amcheck about a problem with one of my client
workstations:
Amanda Backup Client Hosts Check
ERROR: metro: [addr 203.24.38.228: hostname lookup failed]
Client check: 5 hosts checked in 1.692 seconds, 1 problem found
This is nonsense -- I ca
>(gdb) print version_info[21]
>$2 = 0x2
>
>Ack!
No kidding!
>H, gcc version 2.8.1 is what I am using...
Me, too, but on Solaris 2.6.
I don't think this would matter, but what do you get when you run
"gcc -v"? Was it built for the OS version you have (2.7, as I recall)?
The only things I
> One more test:
>
> break main
> run
> print version_info[20] # just to make sure we're looking at
> # the right stuff
> print version_info[21]
gdb) break main
Breakpoint 1 at 0x11a78: file amandad.c, line 116.
(gdb) run
Starting program: /usr/local/lib
>> ... What about version_info[21]?
>
>$1 = 0x2 blah
Good. That's what I expected to see.
>(gdb) break 130
>Breakpoint 1 at 0x11abc: file amandad.c, line 130.
>(gdb) run
>Starting program: /usr/local/libexec/amandad
>warning: Lowest section in /usr/lib/libintl.so.1 is .hash at 0074
>
>Bre
I have installed mtx at /usr/local/bin/mtx
and edited an updated chg-mtx script to reflect this and placed it in
/usr/local/libexec.
when I run
amtape daily current
I get the result:
amtape: could not get changer info: :No such file or directory.
I have not been able to figure out what amtape i
> That all looks reasonable. Unfortunatly, you stopped one short of the
> place amandad is failing :-). What about version_info[21]?
$1 = 0x2 blah
> OK, then try the above first. If that does not show up as a null
> pointer (which it shouldn't since it's what's causing the failure),
> set a
>> What happens if you run "amadmin xx version"?
>...
OK, so at least that works properly (it's basically what amandad is
doing in that loop).
>> and so on until you get to the end of the strings (there should be about
>> 25 of them) or the address is 0x24974 (*vp).
>...
That all looks reasonab
> What happens if you run "amadmin xx version"?
(*insecure*)amanda@atsun01:~$ amadmin atlab version
build: VERSION="Amanda-2.4.1p1"
BUILT_DATE="Tue Jan 23 21:41:04 PST 2001"
BUILT_MACH="SunOS atsun01 5.7 Generic_106541-14 sun4u sparc
SUNW,Ultra-4"
CC="gcc"
paths: bindir="/usr
>> print *vp
>$3 = 0x2
This makes no sense. That data is coming out of a static compiled in
text string.
What happens if you run "amadmin xx version"?
What about:
frame 4
print version_info
print version_info[0]
print version_info[1]
print version_info[2]
and so on until you get
>*** A TAPE ERROR OCCURRED: [[closing tape: I/O error]].
First, an "I/O error" means an I/O error. The tape driver either got
a hardware error or didn't like something itself and reported that back
to Amanda. Amanda never says this itself out of the blue. I don't see
how 2 GB boundaries could
>
> Of what vintage? My amanda server is running
2.2.8-Stable is the ver. Per below, when I run
operator@hades [3:37pm] /usr/local/etc/amanda/master > chio status
picker 0:
slot 0:
slot 1:
slot 2:
slot 3:
slot 4:
slot 5:
slot 6:
drive 0:
this appears ok. amanda works great up to
I used the Amanda FAQ-o-matic "firewalls" entry when I was setting up
backups for a server that sits on the "untrusted" side of an internal
packet filter, and found it helpful -- my thanks to those involved!
However, I was just going over the filtering rules a bit, in order to
clean things up bot
>Date: Wed, 24 Jan 2001 13:45:35 -0600 (CST)
>From: Adam <[EMAIL PROTECTED]>
>Does anyone know if and what changer works with the Exabyte EZ17 7 tape
>changer with the mammoth2 drive?
I'm not using that drive or changer, but...
>We are using Freebsd
Of what vintage? My amanda server is runnin
:
operator@hades [1:27pm] /usr/local/etc/amanda/master > amtape master show
amtape: scanning all 7 slots in tape-changer rack:
slot 1: date 20010124 label VOL1
amtape: could not load slot chio:: /dev/ch0: CHIOMOVE: Invalid argument
and when using chg-scsi shows
operator@hades [1:27pm] /usr/
"Massimo Pinto" <[EMAIL PROTECTED]> writes:
> I have just installed amanda-2.4.1-1 from three rpms (server, client
> and amanda itself) on a Pentium II running a RH6.2 Linux distribution.
> Now I understand there are newer versions of the program but rpms for
> newer versions conflict with old li
>I have Sun L400 Mamoth Tape Drive connected to one E450 server. This is not li
>sted in TAPE list availble with amanda
>2.3.0.4 and also not on the below page.
Where in the world did you find a release of Amanda that ancient?
The latest version is 2.4.2 (www.amanda.org) and is *years* newer
tha
> frame 4# this should put you at "main"
#4 0x11c54 in main (argc=1, argv=0xffbefc04) at amandad.c:174
174 dbprintf(("%s: %s", argv[0], *vp));
> print argv[0]
$1 = 0xffbefcd0 "/usr/local/libexec/amandad"
> print vp
$2 = (char **) 0x24974
> print *vp
$3 = 0x2
> John R.
Thanks John, for your reply.
JRJ => John R. Jackson
JRJ >>1) After a careful search of the files installed from the rpm, it
JRJ >>looks like I have not got any amanda.conf file (strange). ...
JRJ >
JRJ >That's because you need to set all that up yourself, probably by
JRJ >starting with the
>#3 0xff1b3bb0 in debug_printf (format=0x13f10 "%s: %s") at debug.c:62
>#4 0x11c54 in main (argc=1, argv=0xffbefc04) at amandad.c:174
OK, what about the results of this:
frame 4 # this should put you at "main"
print argv[0]
print vp
print *vp
>-Ben
John R. Jackson, T
"Wood, Sid" <[EMAIL PROTECTED]> writes:
> I have been using Amanda (version 2.4.1p1) for about three years as the tool
> with which I backup my servers. Currently I backup an NCR 4400 server
> (MP-RAS 3.02) to an internal DLT-7000. In the past I had experienced
> infrequent errors (vxdump returne
>This is my first message to the list ...
Welcome!
>1) After a careful search of the files installed from the rpm, it
>looks like I have not got any amanda.conf file (strange). ...
That's because you need to set all that up yourself, probably by
starting with the sample that should have been i
> We need the stack traceback. Please do this again and enter "where"
> before "quit".
Sorry bout that.
(gdb) run
Starting program: /usr/local/libexec/amandad
warning: Lowest section in /usr/lib/libintl.so.1 is .hash at 0074
Program received signal SIGSEGV, Segmentation fault.
0xff0b6e94 i
>Is there an Amanda command to verify images sitting in my holding
>disk space? If not I will just run amrecover.
What do you mean by "verify"? No command, including amverify, can
validate an image created by dump, be it on tape or in the holding disk.
It's an unfortunate (and stupid) limitation
>(gdb) run
>Starting program: /usr/local/libexec/amandad
>warning: Lowest section in /usr/lib/libintl.so.1 is .hash at 0074
>
>Program received signal SIGSEGV, Segmentation fault.
>0xff0b6e94 in strlen () from /usr/lib/libc.so.1
>(gdb) quit
We need the stack traceback. Please do this again a
I have just installed amanda-2.4.1-1 from three rpms (server, client
and amanda itself) on a Pentium II running a RH6.2 Linux distribution.
Now I understand there are newer versions of the program but rpms for
newer versions conflict with old libraries that I have and which are,
to me at least, to
>can anyone give me a short explanation of the bread, short read and lseek
>error messages here?
>
> DUMP: bread: lseek fails
>? DUMP: bread: lseek fails
>? DUMP: short read error from /dev/sda10: [block
>-1572797648]: count=4096, got=0
Dump works with what are called inodes and raw disk addr
I have been using Amanda (version 2.4.1p1) for about three years as the tool
with which I backup my servers. Currently I backup an NCR 4400 server
(MP-RAS 3.02) to an internal DLT-7000. In the past I had experienced
infrequent errors (vxdump returned 3), but recently a puzzling anomaly has
surface
> What's your inetd.conf line look like? If you forget the trailing
> command name argument, I've seen amandad fail like this on some systems.
No changes...
amanda dgram udp waitamanda /usr/local/libexec/amandad amandad
> What happens if you run amandad by hand **as the Amanda user*
Here's more info on the changer:
from dmesg:
(scsi0) found at PCI 1/10/0
(scsi0) Wide Channel, SCSI ID=7, 32/255 SCBs
(scsi0) Downloading sequencer code... 392 instructions downloaded
scsi0 : Adaptec AHA274x/284x/294x (EISA/VLB/PCI-Fast
Is there an Amanda command to verify images sitting in my holding
disk space? If not I will just run amrecover.
Can amrecover run from an image left in the holding disk space or
does that image need to be flushed to tape first?
-- Forwarded message --
Date: Wed, 24 Jan 2001 08
>Date: Wed, 24 Jan 2001 15:42:57 + (GMT)
>From: Denise Ives <[EMAIL PROTECTED]>
>show sda10 did its level 1 back up. So did sd10 back up with errors?
It would appear that a backup image was created, and amanda stored it
for you, per your request.
The extent to which that image might be us
>show sda10 did its level 1 back up. So did sd10 back up with errors?
It had some errors but was eventually successful:
>| DUMP: DUMP IS DONE
John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
can anyone give me a short explanation of the bread, short read and lseek
error messages here?
DUMP: bread: lseek fails
? DUMP: bread: lseek fails
? DUMP: short read error from /dev/sda10: [block
-1572797648]: count=4096, got=0
thanks again.
>Jan 23 21:48:58 atsun01 inetd[142]: /usr/local/libexec/amandad: Segmentation
>Fault
What's your inetd.conf line look like? If you forget the trailing
command name argument, I've seen amandad fail like this on some systems.
What happens if you run amandad by hand **as the Amanda user**?
Is /tm
show sda10 did its level 1 back up. So did sd10 back up with errors?
thank much -
(here is some of the output - the output was huge)
FAILURE AND STRANGE DUMP SUMMARY:
lunar1 sda10 lev 1 STRANGE
?
FAILED AND STRANGE DUMP DETAILS:
/-- lunar1 sda10 lev 1 STRANGE
sendbackup: start [ l
Hi,
I have Sun L400 Mamoth Tape Drive connected to one E450 server. This is not listed in
TAPE list availble with amanda
2.3.0.4 and also not on the below page.
http://www.cs.columbia.edu/~sdossick/amanda/
I donot know how I should configure this tape drive? It has two built in drives and
ta
Hi,
I'm having trouble with my Seagate Scorpion 40 (DDS4). It does not
read software labels. I've emulated Amanda like this:
server:~ # rm /tmp/dattest;mtst -f /dev/nst0 rewind;mtst -f /dev/nst0
status; echo;dd if=/dev/nst0 of=/tmp/dattest;echo;cat /tmp/dattest
SCSI 2 tape drive: File number=0,
Hi!
> This error suggests that either you have more than one amdump running
> at the same time, or you have more than one amanda server trying to
> talk to 'fileserver' at the same time, or else you have 'fileserver'
> listed in your disklist with more than one name.
>
> Basically it means that a
jrj wrote:
>When amstatus reports on estimates, are these supposed to be the estimates
>for the volume of data dumped at the specified dump level? ...
Yes. They are the estimates for the level Amanda picked to be done.
>Every day when
>Amanda runs, I see the same huge estimates
On Wed, 24 Jan 2001, Juergen Knott wrote:
> After changing runtapes 1 to runtapes 2, Amanda will not make backups
> I became the following Mail from Amanda:
I don't think runtapes is the only thing that changed.
> FAILURE AND STRANGE DUMP SUMMARY:
> fileserver sdd1 lev 0 FAILED [fileser
Hello Folks,
I'm getting weird timeouts with Solaris 2.7 clients but not with Linux
clients. Here's the debug message:
Amanda 2.4 NAK HANDLE 005-80C20708 SEQ 980329506
ERROR amandad busy
Also, I'm finding that the backups are very slow compared to when done
manually. I used to mount the dire
* Bernhard R. Erdmann <[EMAIL PROTECTED]> (Tue, Jan 23, 2001 at 10:34:35PM +0100)
>>> Work on multitapebackup is (apparently) underway for Amanda NG
>> _This_ is good news indeed. So one possible solution would be
>> to go for a library instead of an autoloader, start with 1 tape
>> of 50 or 100
56 matches
Mail list logo
