Thanks Kenneth.
Johann
--
| Johann Spies Windsorlaan 19 |
| [EMAIL PROTECTED]3201 Pietermaritzburg |
| Tel/Faks Nr. +27 331-46-1310 Suid-Afri
Kenneth Scharf <[EMAIL PROTECTED]> writes:
KS> I read the sources to the latest ftape package (I downloaded the
KS> tarball from the ftape site) and it DOES NOT SUPPORT FORMATING
KS> TAPES.
(for definitions of "it" such that "it" is the Iomega 2GB and Ditto
Max drives. ftape formats tapes fine o
Johann,
The version of ftape in the 2.0.x kernels is much older than that on the
ftape archives. 3.04d is the first version to support the Ditto 2GB
drive, but I understand there are still problems. The latest is 4.02. As
Claus-Justus says on his web page:
If you intend to use Iomega's Di
Chris,
You might trying specifying a block size when you issue the tar command.
On my system, the output of "ftmt -f /dev/ftape status" gives me the block-size
the tape drive is expecting, which I then specify with tar. This fixed for me
the tar problem you described below.
Hope this helps,
-
On Wed, 1 Apr 1998 [EMAIL PROTECTED] wrote:
> The status command didn't provide much info on the tape, in fact it was
> the same for both types of tapes, regular and extended.
>
> % mt -f /dev/ftape status
> drive type = 8423552
> drive status = 0
> sense key error = 0
> residue count = 0
> file
[EMAIL PROTECTED] writes:
> On 1 Apr, Randy Stocking wrote:
> > George Bonser writes:
> >>
> >> How do I determine the maximum capacity? I have inherited a drive
> >> destined to the scrapper. It appears to work just fine after making
> >> a test backup using taper. The kernel reports this on bo
On 1 Apr, Randy Stocking wrote:
> George Bonser writes:
>>
>> How do I determine the maximum capacity? I have inherited a drive
>> destined to the scrapper. It appears to work just fine after making
>> a test backup using taper. The kernel reports this on bootup:
>>
>> QIC-117B drive @1MB/sec
>
George Bonser writes:
>
> How do I determine the maximum capacity? I have inherited a drive
> destined to the scrapper. It appears to work just fine after making
> a test backup using taper. The kernel reports this on bootup:
>
> QIC-117B drive @1MB/sec
> QIC-80 tape
>
> Where would I look to f
On Fri, 16 Jan 1998, Pure Energy wrote:
> Now i download ftape-2.0.30 try to install..
...
> So... any suggestions??? Anyone else out there running this tape drive
> with this kernel?
Hallo Rob,
I am using ftape 3.04-beta with success with my Iomega Ditto 2Gb. The
final version is available. I
On Fri, 16 Jan 1998, Pure Energy wrote:
>
> Well i had put this on the back burner aswell for a short time but have
> put it back in my system. I have just reinstalled an IomegaDitto 2GB tape
> drive (Internal). I run kernel version 2.0.32 (which i need for a specific
> ether card) so i can not r
Andreas Tille wrote:
>
> Hello,
>
> I have a Iomega 250 floppy tape drive. I compiled ftape into
> the Kernel (2.0.30). But what to do to get a device
>/dev/ftape ???
cd /dev
./MAKEDEV ftape
> According to the CDROM-HOWTO I have to create this entry via mknod.
> But what are the correct
On Wed, 28 May 1997 18:28:03 -0400, you wrote:
>I can't really comment on your specific problem as ftape is working
>fine for my Iomega Ditto 800. I think the messages indicate that there
>were write errors on different segments of your tape but the retries
>succeded. You could try to format your
Thanks for your response!
I tracked the problem down to ECC failures. Here is what happens: first time
after format, the ftape gives ECC failures, but taper (the app I was using)
told me that it saw unknown data, and asked me if it should overwrite it...
before I made the connection between the E
On May 28, Igor Grobman wrote
> I recently got myself a Seagate Tapestor3200 TR3/QIC 3020 tape drive. It
> works
> fine under DOS, however when I try to backup anything in Linux, I get the
> following errors:
>
> May 28 19:43:36 whoever kernel: [047]ftape-write.c (ftape_write_segment) -
> write
On Wed, 09 Apr 1997 14:47:54 PDT Ken Gaugler ([EMAIL PROTECTED]) wrote:
> During a dump I noticed these messages in /var/messages:
>
> Apr 9 13:17:18 keng-ppp kernel: [046]ftape-write.c (write_segment)
> - warning: 1 hard error(s) in written segment.
>^^^
Hi Daniel --
You asked:
> Just one question...
>
> Does taper implicitly call 'mt'?
Well, no. In fact, taper does its own ioctl calls, which is why it
is behind the other general-purpose utilities in supporting a broad array
of hardware. I spent a long time studying both taper and tob, and I'm
On Mon, 19 Aug 96 16:33 EDT, [EMAIL PROTECTED]
wrote:
> tar generates a single Tape ARchive (that's why it is called `tar')
> and knows nothing about multiple files or positioning of a tape, it
> just reads or writes from/to a device. mt knows everyting about moving
> the tape back and forth,
:
: There were only two sessions on my tape. Sadly, the second session
: contained the /usr filesystem, so I lost everything :(
Rejoice! you did not lose anything! Just reinstall and restore what you
have. All stuff in usr are executables and other read-only stuff as
per FSSTND. (except if you h
> There were only two sessions on my tape. Sadly, the second session
> contained the /usr filesystem, so I lost everything :(
Whenever doing backups, _verify_ your backups, even if it doubles the time
it takes to do them.
Oh, and whenever you're going to do something dangerous, _double_ your
bac
Ken Gaugler writes:
Ken> I had a nasty surprise using ftape to dump my filesystems for
Ken> archival right before repartitioning my hard drive. I wanted to let
Ken> people know about this in case they were not already aware.
Ken>
Ken> If you plan to dump several filesystems to one t
20 matches
Mail list logo
