SearchFAQMemberlist Log in
Reply to topic Page 1 of 1
amrecover problem
Author Message
Post amrecover problem 
Hello,

When I tried to recover a folder called "my folder" (with space in it, I
don't know if this could be the problem). I have for time to time,
Segment Fault.

and when I try to recover (when I don't receive the error) with the
extract command :

Load tape weekly-05 now
Continue [?/Y/n/s/t]? Y
EOF, check amidxtaped.<timestamp>.debug file on localhost.
amrecover: short block 0 bytes
UNKNOWN file
amrecover: Can't read file header
extract_list - child returned non-zero status: 1


Some hints ??
Thanks !!

--
Frederic Medery
System Administrator

LexUM, University of Montreal

Post amrecover problem 
Hi,

I've had the same message yesterday - I suggest you read the
/tmp/Amanda/amidxtaped.<timestamp>.debug file and post the contents. In
my case amrecover was being passed a '0' for the tapedev instead of a
suitable tape device. This was because it was picking up my chg-scsi
setup, and mapping the device name (0) instead of the device type
(/dev/nst0) to amrestore. I worked around this but using the settape
/dev/nst0 to pick up the tape device directly and avoid the /dev/sg
devices altogether which amrestore couldn't cope with.

Regards,

Bernard McAuley
bernard.mcauley < at > phyworks-ic.com


-----Original Message-----
From: owner-amanda-users < at > amanda.org
[mailto:owner-amanda-users < at > amanda.org]
On Behalf Of Frederic Medery
Sent: 28 June 2004 15:58
To: Mailing List Amanda User
Subject: amrecover problem

Hello,

When I tried to recover a folder called "my folder" (with space in it,
I
don't know if this could be the problem). I have for time to time,
Segment Fault.

and when I try to recover (when I don't receive the error) with the
extract command :

Load tape weekly-05 now
Continue [?/Y/n/s/t]? Y
EOF, check amidxtaped.<timestamp>.debug file on localhost.
amrecover: short block 0 bytes
UNKNOWN file
amrecover: Can't read file header
extract_list - child returned non-zero status: 1


Some hints ??
Thanks !!

--
Frederic Medery
System Administrator

LexUM, University of Montreal

Post amrecover problem 
I had the same prob (the 0 problem). But it's still not working (other
reason). Here is my

amidxtaped... :
amidxtaped: debug 1 pid 1566 ruid 33 euid 33: start at Mon Jun 28
13:21:51 2004
amidxtaped: version 2.4.4p1
amidxtaped: time 0.000: > SECURITY USER root
amidxtaped: time 0.001: bsd security: remote host localhost.localdomain
user root local user amanda
amidxtaped: time 0.002: amandahosts security check passed
amidxtaped: time 0.002: > CONFIG=weekly
amidxtaped: time 0.002: > LABEL=weekly-05
amidxtaped: time 0.002: > FSF=23
amidxtaped: time 0.002: > HEADER
amidxtaped: time 0.002: > DEVICE=/dev/nst0
amidxtaped: time 0.002: > HOST=^urbino$
amidxtaped: time 0.002: > DISK=^/home/users$
amidxtaped: time 0.002: > DATESTAMP=20040529
amidxtaped: time 0.002: > END
amidxtaped: time 0.007: amrestore_nargs=0
amidxtaped: time 0.008: Ready to execv amrestore with:
path = /usr/sbin/amrestore
argv[0] = "amrestore"
argv[1] = "-p"
argv[2] = "-h"
argv[3] = "/dev/nst0"
argv[4] = "^urbino$"
argv[5] = "^/home/users$"
argv[6] = "20040529"
amrestore: WARNING: not at start of tape, file numbers will be offset
amrestore: 0: reached end of information
amidxtaped: time 0.047: amrestore terminated normally with status: 1
amidxtaped: time 0.047: rewinding tape ...
amidxtaped: time 9.815: done
amidxtaped: time 9.815: pid 1566 finish time Mon Jun 28 13:22:00 2004

Frédéric Médery
Administrateur Système
LexUM, Université de Montréal

mederyf < at > lexum.umontreal.ca
tel. : (514) 343-6111 #3288



Bernard McAuley wrote:

Hi,

I've had the same message yesterday - I suggest you read the
/tmp/Amanda/amidxtaped.<timestamp>.debug file and post the contents. In
my case amrecover was being passed a '0' for the tapedev instead of a
suitable tape device. This was because it was picking up my chg-scsi
setup, and mapping the device name (0) instead of the device type
(/dev/nst0) to amrestore. I worked around this but using the settape
/dev/nst0 to pick up the tape device directly and avoid the /dev/sg
devices altogether which amrestore couldn't cope with.

Regards,

Bernard McAuley
bernard.mcauley < at > phyworks-ic.com




-----Original Message-----
From: owner-amanda-users < at > amanda.org


[mailto:owner-amanda-users < at > amanda.org]


On Behalf Of Frederic Medery
Sent: 28 June 2004 15:58
To: Mailing List Amanda User
Subject: amrecover problem

Hello,

When I tried to recover a folder called "my folder" (with space in it,


I


don't know if this could be the problem). I have for time to time,
Segment Fault.

and when I try to recover (when I don't receive the error) with the
extract command :

Load tape weekly-05 now
Continue [?/Y/n/s/t]? Y
EOF, check amidxtaped.<timestamp>.debug file on localhost.
amrecover: short block 0 bytes
UNKNOWN file
amrecover: Can't read file header
extract_list - child returned non-zero status: 1


Some hints ??
Thanks !!

--
Frederic Medery
System Administrator

LexUM, University of Montreal







Post amrecover problem 
On Monday 28 June 2004 15:05, Frederic Medery wrote:
I had the same prob (the 0 problem). But it's still not working
(other reason). Here is my

amidxtaped... :
amidxtaped: debug 1 pid 1566 ruid 33 euid 33: start at Mon Jun 28
13:21:51 2004
amidxtaped: version 2.4.4p1
amidxtaped: time 0.000: > SECURITY USER root
amidxtaped: time 0.001: bsd security: remote host
localhost.localdomain user root local user amanda

What is this^^^^^^? localhost < at > localdomain is not a valid, unique
adress and will not work for recovery. Please read the FAQ and
TOP-TEN-QUESTIONS in the docs directory of the tarball.

amidxtaped: time 0.002: amandahosts security check passed
amidxtaped: time 0.002: > CONFIG=weekly
amidxtaped: time 0.002: > LABEL=weekly-05
amidxtaped: time 0.002: > FSF=23
amidxtaped: time 0.002: > HEADER
amidxtaped: time 0.002: > DEVICE=/dev/nst0
amidxtaped: time 0.002: > HOST=^urbino$
amidxtaped: time 0.002: > DISK=^/home/users$
amidxtaped: time 0.002: > DATESTAMP=20040529
amidxtaped: time 0.002: > END
amidxtaped: time 0.007: amrestore_nargs=0
amidxtaped: time 0.008: Ready to execv amrestore with:
path = /usr/sbin/amrestore
argv[0] = "amrestore"
argv[1] = "-p"
argv[2] = "-h"
argv[3] = "/dev/nst0"
argv[4] = "^urbino$"
argv[5] = "^/home/users$"
argv[6] = "20040529"
amrestore: WARNING: not at start of tape, file numbers will be
offset amrestore: 0: reached end of information
amidxtaped: time 0.047: amrestore terminated normally with status: 1
amidxtaped: time 0.047: rewinding tape ...
amidxtaped: time 9.815: done
amidxtaped: time 9.815: pid 1566 finish time Mon Jun 28 13:22:00
2004

Frédéric Médery
Administrateur Système
LexUM, Université de Montréal

mederyf < at > lexum.umontreal.ca
tel. : (514) 343-6111 #3288

Bernard McAuley wrote:
Hi,

I've had the same message yesterday - I suggest you read the
/tmp/Amanda/amidxtaped.<timestamp>.debug file and post the
contents. In my case amrecover was being passed a '0' for the
tapedev instead of a suitable tape device. This was because it
was picking up my chg-scsi setup, and mapping the device name (0)
instead of the device type (/dev/nst0) to amrestore. I worked
around this but using the settape /dev/nst0 to pick up the tape
device directly and avoid the /dev/sg devices altogether which
amrestore couldn't cope with.

Regards,

Bernard McAuley
bernard.mcauley < at > phyworks-ic.com

-----Original Message-----
From: owner-amanda-users < at > amanda.org

[mailto:owner-amanda-users < at > amanda.org]

On Behalf Of Frederic Medery
Sent: 28 June 2004 15:58
To: Mailing List Amanda User
Subject: amrecover problem

Hello,

When I tried to recover a folder called "my folder" (with space in
it,

I

don't know if this could be the problem). I have for time to time,
Segment Fault.

and when I try to recover (when I don't receive the error) with
the extract command :

Load tape weekly-05 now
Continue [?/Y/n/s/t]? Y
EOF, check amidxtaped.<timestamp>.debug file on localhost.
amrecover: short block 0 bytes
UNKNOWN file
amrecover: Can't read file header
extract_list - child returned non-zero status: 1


Some hints ??
Thanks !!

--
Frederic Medery
System Administrator

LexUM, University of Montreal

--
Cheers, Gene
There are 4 boxes to be used in defense of liberty.
Soap, ballot, jury, and ammo.
Please use in that order, starting now. -Ed Howdershelt, Author
Additions to this message made by Gene Heskett are Copyright 2004,
Maurice E. Heskett, all rights reserved.

Post amrecover problem 
Frederic Medery wrote:

I had the same prob (the 0 problem). But it's still not working (other
reason). Here is my

amidxtaped... :
amidxtaped: debug 1 pid 1566 ruid 33 euid 33: start at Mon Jun 28
13:21:51 2004
amidxtaped: version 2.4.4p1
amidxtaped: time 0.000: > SECURITY USER root
amidxtaped: time 0.001: bsd security: remote host localhost.localdomain

I hope you understand that this only works when server == client.
Not very scalable, for a client-server tool.

user root local user amanda
amidxtaped: time 0.002: amandahosts security check passed
amidxtaped: time 0.002: > CONFIG=weekly
amidxtaped: time 0.002: > LABEL=weekly-05
amidxtaped: time 0.002: > FSF=23
amidxtaped: time 0.002: > HEADER
amidxtaped: time 0.002: > DEVICE=/dev/nst0
amidxtaped: time 0.002: > HOST=^urbino$
amidxtaped: time 0.002: > DISK=^/home/users$
amidxtaped: time 0.002: > DATESTAMP=20040529
amidxtaped: time 0.002: > END
amidxtaped: time 0.007: amrestore_nargs=0
amidxtaped: time 0.008: Ready to execv amrestore with:
path = /usr/sbin/amrestore
argv[0] = "amrestore"
argv[1] = "-p"
argv[2] = "-h"
argv[3] = "/dev/nst0"
argv[4] = "^urbino$"
argv[5] = "^/home/users$"
argv[6] = "20040529"
amrestore: WARNING: not at start of tape, file numbers will be offset

Here is your warning. Amanda did not find the image from where it
started to end of tape. You have to rewind the tape manually (with
a command 'mt rewind" I mean Smile ), or add these two directives
to amanda.conf:

amrecover_do_fsf yes # this implies a rewind
amrecover_check_label yes

Because of a little bug in your version you need both parameters set
to yes (that bug is solved in 2.4.4p3).


On Behalf Of Frederic Medery
When I tried to recover a folder called "my folder" (with space in it,
don't know if this could be the problem). I have for time to time,
Segment Fault.

This is probably a complete other problem. Is it repeatable?
Can you send the debug file of such a restore attempt?
Can you find out what program is hit by the segmention fault?
(amindexd, gzip, gnutar...)? Any core file (if "ulimit -c" is
set sufficiently large) in /tmp/amanda on the server?


--
Paul Bijnens, Xplanation Tel +32 16 397.511
Technologielaan 21 bus 2, B-3001 Leuven, BELGIUM Fax +32 16 397.512
http://www.xplanation.com/ email: Paul.Bijnens < at > xplanation.com
***********************************************************************
* 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, Very Happy:Very Happy, 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 *
***********************************************************************

Display posts from previous:
Reply to topic Page 1 of 1
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
  


Magic SEO URL for phpBB