Hi Frank,

Are you sure the block size is the same between tar and ftape?  This
could cause this type of problem.  If I recall ftape ha a 10k block
size, but I don't remember tar's default size.

Carl

On 28-Dec-98 Frank Paprosky wrote:
> Hi! 
> 
> I can't make it work with the ftape version 4.02 ????
> 
> Can you help ????
> 
> Here's a sample of /usr/adm/messages after a tar cvzf /dev/ftape *
> 
> Dec 28 08:23:41 progidev kernel: [099] 0    ftape-rw.c (seek_forward)
> -
> read_id failed completely.
> Dec 28 08:23:42 progidev kernel: [100] 0    ftape-rw.c
> (determine_position)
> - ftape_report_drive_status: 0x24.
[snipped]

> panic: location not known.
> Dec 28 08:25:21 progidev kernel: [194] 0   ftape-rw.c
> (ftape_start_tape) -
> failed to reposition.
> Dec 28 08:25:21 progidev kernel: [195] 0  ftape-read.c
> (ftape_read_segment_R2e5a9d01) - Error: segment 0 unreachable.
> Dec 28 08:25:21 progidev kernel: [196] 0 ftape-read.c
> (ftape_read_header_segment_Rfe770942) - header segment damaged,
> trying
> backup.
> Dec 28 08:25:21 progidev kernel: [197] 0  ftape-read.c
> (ftape_read_segment_R2e5a9d01) - interrupted by non-blockable signal.
> Dec 28 08:25:21 progidev kernel: [198] 0 ftape-read.c
> (ftape_read_header_segment_Rfe770942) - No deblock buffer.
> 
> 
> I've stopped the backup with Ctrl-C. I've also tried several tapes
> before
> writting this e-mail. I've tried to format a tape with "ftformat", it
> also
> failed....
> 
> Note: Kernel version 2.0.33
> 
> What should I do to make it work ?

----------------------------------
E-Mail: Carl J. Nobile <[EMAIL PROTECTED]>
Date: 28-Dec-98
Time: 17:41:28
----------------------------------

Reply via email to