From: Mikael Pettersson <mikpe@csd.uu.se>
To: linux-kernel@vger.kernel.org, solon@macaulay.demon.co.uk
Subject: Re: Ftape bug
Date: Wed, 10 Jan 2001 01:33:52 +0100 (MET) [thread overview]
Message-ID: <200101100033.BAA04606@harpo.it.uu.se> (raw)
On Tue, 9 Jan 2001, Tony Sumner wrote:
>I have a problem with ftape. What happened was that I had a backup on
>QIC80 tape that I made from Red Hat 5.2 and I (foolishly?) installed
>SuSE 7.0. I then found I could not read the tape with the newer version
>of ftape.
>...
>Kernel version: was 2.0.36, now 2.2.16
>
>ftape version: 3.04d
>...
>what went wrong: tob reported 'No input'. The log in /var/spool/messages
> had a report from ftape to say that it was looking at a
> new cartridge. An extract from the log is below. It was not
> a new cartridge -- I have been able to read it by reloading
> kernel 2.0.36 and the corresponding version 2.08 of ftape.
Right. I'm pretty sure ftape-3.04d (as included in current 2.2 and 2.4
kernels) doesn't maintain read-compatibility with ftape-2.08. (See
Documentation/ftape.txt "Changes", and drivers/char/ftape/RELEASE-NOTES
about "sftape" being gone.)
I think your best bet is to read the tape using your 2.0.36 kernel
with ftape 2.08, reboot into 2.2.16, format the tape (or get a new one),
and then dump the data again using ftape 3.04d. Oh, and DON'T use the
built-in compression support. It's gone in ftape 4 :-)
>I am not a subscriber to this mailing list so I was advised to ask
>you to Cc any reply to me at solon@macaulay.demon.co.uk
/Mikael
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next reply other threads:[~2001-01-10 0:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-10 0:33 Mikael Pettersson [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-01-09 17:26 Tony Sumner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200101100033.BAA04606@harpo.it.uu.se \
--to=mikpe@csd.uu.se \
--cc=linux-kernel@vger.kernel.org \
--cc=solon@macaulay.demon.co.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®