I've seen similar error msg (short block, can't read header) on first attempt to recover from tapes just-written and left in my Exabyte 8900 tape drive. Problem disappeared after a) I explicitly rewound the tape and/or (I'm not sure which) b) the tape automatically rewound after the first amrecover error.
I assume (since the taping device must be specified non-rewinding) that amrecover hiccuped because it didn't automatically rewind before trying to read, and so started off at EOT. I hope that's the correct explanation... Robert L. Becker, Jr. Col, USAF, MC Department of Cellular Pathology Armed Forces Institute of Pathology Washington, DC 20306-6000 301-319-0300 On Thu, 6 Jun 2002, Fabien SEISEN wrote: > > Hi, > > i use amanda 2.4.2p2 (2.4.2p2-4 on Debian woody). > When i try to recover a file: > > amrecover> cd toto/ > amrecover> add tata.html > amrecover> extract > > i got: > EOF, check amidxtaped.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 > > and i could'nt find the file "amidxtaped.debug". > > It append at least with one file (not all files :) > > but if i do: > amrecover> add toto > amrecover> extract > > it successfully restore directory "toto" with tata.html inside > > -- > Fabien Seisen [EMAIL PROTECTED] dakol@opn > GnuPG ID 1024D/112189D8 >
