From: Kern Sibbald <kern@sibbald.com>
To: Willem Riede <wrlk@riede.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Kai Makisara <Kai.Makisara@kolumbus.fi>,
linux-scsi@vger.kernel.org
Subject: Re: Linux tape drivers
Date: Wed, 4 Apr 2007 16:26:14 +0200 [thread overview]
Message-ID: <200704041626.15298.kern@sibbald.com> (raw)
In-Reply-To: <150283e90704032000p7f447a26pe3752b22024a1b67@mail.gmail.com>
On Wednesday 04 April 2007 05:00, Willem Riede wrote:
> > Kern Sibbald <kern@sibbald.com> wrote:
...
Hello Willem,
>
> Osst supports both scsi and ide models of the Onstream dirves it is
> designed for.
> It uses ide-scsi for the ide model. In the past, I did look at
> ide-tape to see if it could be made to work properly for the ide
> Onstream tape, but that would have taken so much work, I decided to
> limit myself to ide-scsi.
>
> For other ide tape drives, the same could be done, using Kai's st
> driver (of which osst is a clone). Ide-tape could be deprecated, left
> to use for drives/applications it happens to work for. Given that the
> new sata world is using st also, this concentrates effort where it has
> maximum leverage.
I'm all in favor of deprecating ide-tape if ide-scsi is a viable alternative,
and if that is the only one you kernel guys would like to support. Let's
concentrate on the drivers that will be the most important over the next few
years (SATA?)
>
> If there are issues using Bacula on ide drives with ide-scsi and st,
> we should debug those. If my previous experience getting osst to work
> properly with Bacula can be of any use, I'll be happy to help where I
> can.
Your previous experience could be particularly helpful. Thanks for the offer.
I'm in the process of taking a mini-Bacula survey of the problems. Here are
the results for the moment:
===
Sebastiaan: He returned his Quantum DLT-V4 SATA drive, which did not work with
Bacula, in exchange for a SCSI drive.
Bob: He has a SDX-260V ATAPI AIT-E and reports the following:
1. Sony SDX-260V
2. ATAPI
3. Tried both ide-scsi and ide-tape
4. ide-scsi simply locked up my machine after ANY attempt to write data
to the tape. I tried various combinations of block sizes and such.
ide-tape would wirte to the tape and could read it but failed the
positioning tests under btape. Specifically it would read any block
from the first file on the tape. When a block from the second file was
requested, the machine would lock up.
5. Gentoo Linux 2.6.20 - gcc 4.1.2 - glibc 2.5 - paludis 0.22.2 - bacula
2.0.3
Robert: Reports:
A year ago I used the IDE drive on Linux. If I remember
correctly the problem only occurred when using DMA, PIO worked but was very,
very slow. The symptoms changed depending on whether I used the
SCSI driver stack or the ide-tape driver; but neither worked properly.
===
Please tell me the best way to proceed. I don't have the hardware, but
understand Bacula, the users have the hardware, but don't understand Bacula's
needs (Robert knows Bacula in detail) -- not the best of situations. I will
buy the hardware if required, but I'd like to limit ($$$) to what is going to
be mostly used in the future.
On the other general issues of the tape API (read/write/open/ioctl), I briefly
sketched my problems/concerns. If anyone is interested in any of those
points, I can be a lot more specific.
next prev parent reply other threads:[~2007-04-04 14:26 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200704031508.37222.kern@sibbald.com>
2007-04-03 20:39 ` Linux tape drivers Andrew Morton
2007-04-03 21:30 ` Kern Sibbald
2007-04-03 21:57 ` Andrew Morton
2007-04-03 22:15 ` James Bottomley
2007-04-04 3:00 ` Willem Riede
2007-04-04 14:26 ` Kern Sibbald [this message]
2007-04-04 18:55 ` Andrew Morton
2007-04-04 19:21 ` Kern Sibbald
2007-04-04 20:37 ` Andrew Morton
2007-04-04 19:22 ` Willem Riede
2007-04-04 20:39 ` Andrew Morton
2007-04-04 21:31 ` Bartlomiej Zolnierkiewicz
2007-04-04 21:43 ` Andrew Morton
2007-04-04 18:46 ` Kai Makisara
2007-04-04 19:50 ` Douglas Gilbert
2007-04-04 20:58 ` Kern Sibbald
2007-04-04 21:54 ` Kai Makisara
2007-04-05 8:32 ` Kern Sibbald
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=200704041626.15298.kern@sibbald.com \
--to=kern@sibbald.com \
--cc=Kai.Makisara@kolumbus.fi \
--cc=akpm@linux-foundation.org \
--cc=linux-scsi@vger.kernel.org \
--cc=wrlk@riede.org \
/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