public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Bill Davidsen <davidsen@tmr.com>
To: Gene Heskett <gene.heskett@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: speed trends in pata world.
Date: Thu, 05 Jul 2007 18:11:33 -0400	[thread overview]
Message-ID: <468D6C95.4070008@tmr.com> (raw)
In-Reply-To: <200707041550.22533.gene.heskett@gmail.com>

Gene Heskett wrote:
> Greetings;
> 
> The drive speeds seem to be going the wrong way.  Its an nforce2 equipt mobo, 
> and I have 3 drives currently in this box.  Running 2.6.22-rc6-cfs-v18 + the 
> ftdi_sio.c patch.
> 
> hda, the primary on cable 0, is running at around 28MB/Sec.  Its a 200GB WD 
> about 2 years old.
> 
> hdb, is running at around 79MB/Sec, its a 4 year old 120GB WD.
> hdd is running at about 75MB/Sec, is a nearly new 300GB WD.
> 
> Can I read anything into the fact that the 2 fast drives are on the slave end 
> of the cables, whereas the slow one is master in the middle of the cable?
> 
First look at dmesg and see what it tells you. Second, if there is a 
slow device on the cable it will sometimes limit the speed of the disk. 
Alan Cox and God might know why, I don't.

Third, you can play with drive parameters with hdparm. *DANGEROUS* to do 
so, the man page says "needless and risky," but at least the older 
kernels truly sucked at guessing the correct speeds. Backups are advised 
if you do this, etc,etc.

-- 
Bill Davidsen <davidsen@tmr.com>
   "We have more to fear from the bungling of the incompetent than from
the machinations of the wicked."  - from Slashdot

      parent reply	other threads:[~2007-07-09 11:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-04 19:50 speed trends in pata world Gene Heskett
2007-07-04 21:13 ` Thomas Backlund
2007-07-05 22:11 ` Bill Davidsen [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=468D6C95.4070008@tmr.com \
    --to=davidsen@tmr.com \
    --cc=gene.heskett@gmail.com \
    --cc=linux-kernel@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