I run ftape-4.03-pre-2 with ftape-tools-1.07 on a Linuxkernel.2.0.35
with Linux modutils 2.1.85 and a Teak 800 internal tapedrive.
As I said in the subject, I cannot add another volume to the tape. Whenever I
trie, it starts from the beginning overwriting what has been written there.
I tried all the commands like:
'ftmt -f /dev/nqft0 eom' or 'ftmt -f /dev/nqft0 fsf'. It doesnt help.
Ftape and zftape load allright.
ftape-internal gives the following in /var/log/messages:
i cannot find anything wrong with that.
--------------------------------------------------------------------------
...
Feb 3 16:36:16 vitzlipu kernel: zftape for ftape v4.03-pre-2 11/05/98
Feb 3 16:36:16 vitzlipu kernel: (c) 1996, 1997 Claus-Justus Heine
([EMAIL PROTECTED])
Feb 3 16:36:16 vitzlipu kernel: vfs interface for ftape floppy tape driver.
Feb 3 16:36:16 vitzlipu kernel: Support for QIC-113 compatible volume table.
Feb 3 16:36:16 vitzlipu kernel: Compiled for Linux version 2.0.35
Feb 3 16:36:16 vitzlipu kernel: [000] zftape-init.c (zft_init) - zft_init @
0x0684f98c.
Feb 3 16:36:16 vitzlipu kernel: [001] zftape-init.c (zft_init) - installing zftape
VFS interface for ftape driver ....
Feb 3 16:36:38 vitzlipu kernel: fdc-internal.c: fdc_internal_register @ 0x068577e4.
Feb 3 16:36:38 vitzlipu kernel: [002] fdc-io.c (fdc_register) - Probing for
ftape-internal tape drive slot 0.
Feb 3 16:36:38 vitzlipu kernel: [003] 0 fdc-internal.c (_fdc_int_detect) - called
with count 0.
Feb 3 16:36:38 vitzlipu kernel: [004] 0 fdc-internal.c (fdc_int_request_regions) -
address 0x3f0 occupied (by floppy drive
r?), using it anyway.
Feb 3 16:36:38 vitzlipu kernel: [005] 0 fdc-internal.c (_fdc_int_detect) - fdc[0]
base: 0x03f0, irq: 6, dma: 2.
Feb 3 16:36:38 vitzlipu kernel: [006] 0 ftape-buffer.c (add_one_buffer) - buffer nr
#1 @ 0500d098, dma area @ 006f0000.
Feb 3 16:36:38 vitzlipu kernel: [007] 0 ftape-buffer.c (add_one_buffer) - buffer nr
#2 @ 0500d798, dma area @ 00c18000.
Feb 3 16:36:38 vitzlipu kernel: [008] 0 ftape-buffer.c (add_one_buffer) - buffer nr
#3 @ 0500d698, dma area @ 003b8000.
Feb 3 16:36:38 vitzlipu kernel: [009] fdc-io.c (fdc_register) - Probing for
ftape-internal tape drive slot 1.
Feb 3 16:36:38 vitzlipu kernel: [010] 1 fdc-internal.c (_fdc_int_detect) - called
with count 1.
Feb 3 16:36:38 vitzlipu kernel: [011] fdc-io.c (fdc_register) - Probing for
ftape-internal tape drive slot 2.
Feb 3 16:36:38 vitzlipu kernel: [012] 2 fdc-internal.c (_fdc_int_detect) - called
with count 2.
Feb 3 16:36:38 vitzlipu kernel: [013] fdc-io.c (fdc_register) - Probing for
ftape-internal tape drive slot 3.
Feb 3 16:36:38 vitzlipu kernel: [014] 3 fdc-internal.c (_fdc_int_detect) - called
with count 3.
Feb 3 16:36:38 vitzlipu kernel: fdc-internal.c: fdc_internal_register @ 0x068577e4.
---------------------------------------------------------------------------
also I get:
--------------------------------------
...
Feb 3 17:06:16 vitzlipu kernel: [202] 0 ftape-io.c (ftape_report_operation) -
timeout on Acknowledge.
Feb 3 17:06:16 vitzlipu kernel: [203] 0 ftape-io.c
(ftape_report_raw_drive_status) - report_operation failed after 4 trials.
Feb 3 17:06:16 vitzlipu kernel: [204] 0 ftape-io.c (ftape_wakeup_drive) -
ftape_report_raw_drive_status(ftape, &status) failed: -5.
Feb 3 17:06:16 vitzlipu kernel: [205] 0 ftape-ctl.c (ftape_activate_drive) - known
wakeup method failedTrying all the (four) others ....
----------------------------------------------------------------------
...whenever I send a command to ftape. This seems to be more fatal.
What can I do?
Any help is very much appreciated.
--
Hartmut Gehrke-Tschudi
