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 [EMAIL PROTECTED] > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > 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
