All of lore.kernel.org
 help / color / mirror / Atom feed
From: James Pearson <james-p@moving-picture.com>
To: linux-scsi@vger.kernel.org
Subject: LTO-3 read performance issues
Date: Wed, 07 Nov 2007 15:18:05 +0000	[thread overview]
Message-ID: <4731D72D.5000404@moving-picture.com> (raw)

I have two LTO-3 (QUANTUM ULTRIUM 3) drives attached to a dual Adaptec 
U160 controller (one per SCSI host) on a Dell PE2850 running a RHEL4 
based kernel (2.6.9 based).

I'm trying to read (with tar) LTO-3 tapes written on another system 
(possibly an SGI IRIX box), but I'm getting extremely variable read 
rates - from a few Kb/s to tens of Mb/s - while reading the same tape

After a bit of trial and error, it looks like the tapes have been 
written in variable block mode with a block size of 16Kb

To list the tapes, I need to set the block size to 0 (mt setblk 0) and run:

tar tvfb $TAPE 32

Running strace on the tar process shows that it does a number of 
read()'s then 'sticks' on a read() for a number of seconds, and then 
does a burst of read()'s - the number of reads it does in these bursts 
and the time if waits on a particular read vary.

My guess this is something to do the drive having to repositioning the 
tape between reads and breaking the tape streaming ...

I get the same issue on both drives with different tapes from the same 
source.

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?

Thanks

James Pearson


             reply	other threads:[~2007-11-07 15:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-07 15:18 James Pearson [this message]
2007-11-07 18:37 ` LTO-3 read performance issues Kai Makisara
2007-11-08 15:10   ` James Pearson

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=4731D72D.5000404@moving-picture.com \
    --to=james-p@moving-picture.com \
    --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.