From: James Pearson <james-p@moving-picture.com>
To: Kai Makisara <Kai.Makisara@kolumbus.fi>
Cc: linux-scsi@vger.kernel.org
Subject: Re: LTO-3 read performance issues
Date: Thu, 08 Nov 2007 15:10:07 +0000 [thread overview]
Message-ID: <473326CF.8060102@moving-picture.com> (raw)
In-Reply-To: <alpine.LSU.0.9999.0711072022370.7663@kai.makisara.local>
Kai Makisara wrote:
>>
>>I am using the default st module options and not doing anything other than
>>using 'mt setblk 0'.
>>
>>Is there anything I can do to get a decent, sustained read rate from these
>>tapes?
>>
>
> If your system can process the data fast enough and the tape blocks are of
> the same size, you can try using fixed block mode and buffered transfers.
> This allows the driver to use larger SCSI reads. You have to load the st
> module with parameter buffer_kbs=xxx, where xxx is, for instance, 1024 (1
> MB buffer). You also have to disable direct i/o with the module parameter
> try_direct_io=0 (otherwise buffered transfers are disabled).
Thanks, I tried that, but it makes no difference. I also tried
increasing the buffer_kbs size by doubling it a few times, but that made
no difference either
I have now found out that the tapes were written on an SGI system -
using a fixed block device and the default options to tar. However, I
have to either use 'mt setblk 0' or 'mt setblk 16384' to read anything
from these tapes.
Just to check that nothing is wrong with my system, I can read an LTO-3
tape previously written on my system, using the default options to tar
and the st module - and I get over 40Mb/s on reads, compared with about
400Kb/s I'm getting with these problematic tapes ...
Is there anything else I can do to read these tapes at a decent speed?
Thanks
James Pearson
prev parent reply other threads:[~2007-11-08 15:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-07 15:18 LTO-3 read performance issues James Pearson
2007-11-07 18:37 ` Kai Makisara
2007-11-08 15:10 ` James Pearson [this message]
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=473326CF.8060102@moving-picture.com \
--to=james-p@moving-picture.com \
--cc=Kai.Makisara@kolumbus.fi \
--cc=linux-scsi@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.