> This problem was fixed after the 2.5.0p2 release, use CVS or the latest > 2.5.0p2 snapshot from > http://www.iro.umontreal.ca/~martinea/amanda/
Using any release later than 2.4.5p1 I still cannot restore any files from the holding disk. Is there a chance this too is fixed in a snapshot? Here's an example amrecover session: amrecover> add ftpusers Added /opt/sfw/etc/ftpusers amrecover> extract Extracting files from holding disk on host whimsy. The following files are needed: /home1/dumps/amanda/20060501190001/ambiance.med.utah.edu.sdc1.0 Restoring files into directory /tmp Continue [?/Y/n]? Extracting from file /home1/dumps/amanda/20060501190001/ambiance.med.utah.edu.sdc1.0 tar: Read 2541 bytes from - tar: Unexpected EOF in archive tar: Error is not recoverable: exiting now amrecover: Extractor child exited with status 2 extract_list - child returned non-zero status: 1 Continue [?/Y/n/r]? amrecover> -- Monday - Thursday I dump to the holding disk then amflush everything to tape Friday. Each night I get "taper: FATAL syncpipe_get: r: unexpected EOF" in my log when using 2.5. TIA, Steve -- Steven J. Backus Computer Specialist University of Utah E-Mail: [EMAIL PROTECTED] Biomedical Informatics Alternate: [EMAIL PROTECTED] 391 Chipeta Way -- Suite D150 Office: 801.587.9308 Salt Lake City, UT 84108-1266 http://www.math.utah.edu/~backus
