public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Denny Page <denny@cococafe.com>
To: Gerhard Schneider <gs@ilsb.tuwien.ac.at>
Cc: linux-scsi@vger.kernel.org
Subject: Re: SCSI tape access on 2.6 kernels?
Date: Tue, 24 Jan 2006 11:43:37 -0800	[thread overview]
Message-ID: <43D68369.1050307@cococafe.com> (raw)
In-Reply-To: <43D604AD.6050607@ilsb.tuwien.ac.at>

Gerhard,

You may want to test earlier versions of 2.6.  There have been various 
reports of problems with scsi tape in later versions of the 2.6 kernel.  
I have problems beginning with 2.6.14 with U320 with LTO-2, others have 
reported problems going back to 2.6.12.

Denny


Gerhard Schneider wrote:
> It's getting me mad..
>
> It seems that with 2.6 (compared to 2.4) there has something been
> changed in the kernel that I'm not aware of so I'm not able to
> write/read tapes efficiently anymore..
>
> LSI1030 SCSI controller
> Overland tape library
> Seagate LTO-1 tape drive
>
> Kernel 2.4.29:
>
> dd if=linux-2.6.16-rc1.tar.gz of=/dev/nst0 bs=64k
> 776+1 records in
> 776+1 records out
> 50918460 bytes transferred in 4.620612 seconds (11019852 bytes/sec)
>
> Kernel 2.6.14rc1:
>
> dd if=linux-2.6.16-rc1.tar.gz of=/dev/nst0 bs=64k
> 776+1 records in
> 776+1 records out
> 50918460 bytes transferred in 20.395567 seconds (2496545 bytes/sec)
>
> Another machine w/
> LSI1030 SCSI controller
> Megaraid ZCR controller
> Overland tape library
> HP LTO-3 tape drive
> Kernel 2.6.14rc1:
>
> dd if=linux-2.6.16-rc1.tar.gz of=/dev/nst0 bs=64k
> 776+1 records in
> 776+1 records out
> 50918460 bytes transferred in 45.953133 seconds (1108052 bytes/sec)
>
> Either there is an initialization problems with tape drives on 2.6.*
> (I don't think so) or there are tunable kernel parameters that
> I don't know..
>
> CPU load on 2.6 is minimal, tape is waiting for data..
>
> Any idea? (I can provide you with any amount of data etc..)
>
>                                             GS
>
>   

  parent reply	other threads:[~2006-01-24 19:43 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-24 10:42 SCSI tape access on 2.6 kernels? Gerhard Schneider
2006-01-24 12:56 ` Gerhard Schneider
2006-01-24 17:52 ` Chip Coldwell
2006-01-24 20:23   ` Patrick Mansfield
2006-01-24 20:36     ` Chip Coldwell
2006-01-25 21:10       ` Kai Makisara
2006-01-26 16:11         ` Chip Coldwell
2006-01-26 16:39           ` Chip Coldwell
2006-01-26 17:39             ` Dead Adaptec AHA-2940U2/U2W while ripping a CD Mathieu Chouquet-Stringer
2006-01-26 21:54           ` SCSI tape access on 2.6 kernels? Kai Makisara
2006-01-27 15:40             ` Chip Coldwell
2006-01-27 17:56               ` Kai Makisara
2006-01-24 20:56   ` Kai Makisara
2006-01-24 20:58     ` Chip Coldwell
2006-01-24 21:01     ` Gerhard Schneider
2006-01-25 16:08       ` Chip Coldwell
2006-01-25 16:25         ` Denny Page
2006-01-25 19:03           ` Gerhard Schneider
2006-01-24 19:43 ` Denny Page [this message]
2006-01-24 20:50 ` Kai Makisara
2006-01-24 21:12   ` Gerhard Schneider
2006-01-25 21:26   ` Kai Makisara

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=43D68369.1050307@cococafe.com \
    --to=denny@cococafe.com \
    --cc=gs@ilsb.tuwien.ac.at \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox