From: "Jonathan Vardy" <jonathanv@explainerdc.com>
To: "Peter L. Ashford" <ashford@sdsc.edu>,
Stephan van Hienen <raid@a2000.nu>
Cc: Jonathan Vardy <jonathan@explainerdc.com>,
linux-raid@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: RAID 5 performance problems
Date: Fri, 4 Apr 2003 00:09:24 +0200 [thread overview]
Message-ID: <00bf01c2fa2d$afafedd0$2e77c23e@pentium4> (raw)
In-Reply-To: Pine.GSO.4.30.0304031334070.20118-100000@multivac.sdsc.edu
> OK. We've found a potential issue. Are the disks being identified as
> UDMA-33 or UDMA-66/100/133? The performance numbers agree too closely for
> this to be a coincidence. Check the boot logs.
I looked into /var/log/dmesg and found this:
blk: queue c0393144, I/O limit 4095Mb (mask 0xffffffff)
hda: 39062500 sectors (20000 MB) w/2048KiB Cache, CHS=2431/255/63, UDMA(33)
blk: queue c03934a8, I/O limit 4095Mb (mask 0xffffffff)
hdc: 234441648 sectors (120034 MB) w/2048KiB Cache, CHS=232581/16/63,
UDMA(33)
blk: queue c039380c, I/O limit 4095Mb (mask 0xffffffff)
hde: 234441648 sectors (120034 MB) w/2048KiB Cache, CHS=232581/16/63,
UDMA(33)
blk: queue c0393b70, I/O limit 4095Mb (mask 0xffffffff)
hdg: 234441648 sectors (120034 MB) w/2048KiB Cache, CHS=232581/16/63,
UDMA(33)
blk: queue c0393ed4, I/O limit 4095Mb (mask 0xffffffff)
hdi: 234441648 sectors (120034 MB) w/2048KiB Cache, CHS=232581/16/63,
UDMA(33)
blk: queue c0394238, I/O limit 4095Mb (mask 0xffffffff)
hdk: 234441648 sectors (120034 MB) w/2048KiB Cache, CHS=232581/16/63,
UDMA(33)
This is what you meant?
but after the boot I set hdparm manually for each drive with the following
settings:
hdparm -a8 -A1 -c1 -d1 -m16 -u1 /dev/hdc.
WARNING: multiple messages have this Message-ID (diff)
From: "Jonathan Vardy" <jonathanv@explainerdc.com>
To: "Peter L. Ashford" <ashford@sdsc.edu>,
"Stephan van Hienen" <raid@a2000.nu>
Cc: "Jonathan Vardy" <jonathan@explainerdc.com>,
<linux-raid@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: RAID 5 performance problems
Date: Fri, 4 Apr 2003 00:09:24 +0200 [thread overview]
Message-ID: <00bf01c2fa2d$afafedd0$2e77c23e@pentium4> (raw)
In-Reply-To: Pine.GSO.4.30.0304031334070.20118-100000@multivac.sdsc.edu
> OK. We've found a potential issue. Are the disks being identified as
> UDMA-33 or UDMA-66/100/133? The performance numbers agree too closely for
> this to be a coincidence. Check the boot logs.
I looked into /var/log/dmesg and found this:
blk: queue c0393144, I/O limit 4095Mb (mask 0xffffffff)
hda: 39062500 sectors (20000 MB) w/2048KiB Cache, CHS=2431/255/63, UDMA(33)
blk: queue c03934a8, I/O limit 4095Mb (mask 0xffffffff)
hdc: 234441648 sectors (120034 MB) w/2048KiB Cache, CHS=232581/16/63,
UDMA(33)
blk: queue c039380c, I/O limit 4095Mb (mask 0xffffffff)
hde: 234441648 sectors (120034 MB) w/2048KiB Cache, CHS=232581/16/63,
UDMA(33)
blk: queue c0393b70, I/O limit 4095Mb (mask 0xffffffff)
hdg: 234441648 sectors (120034 MB) w/2048KiB Cache, CHS=232581/16/63,
UDMA(33)
blk: queue c0393ed4, I/O limit 4095Mb (mask 0xffffffff)
hdi: 234441648 sectors (120034 MB) w/2048KiB Cache, CHS=232581/16/63,
UDMA(33)
blk: queue c0394238, I/O limit 4095Mb (mask 0xffffffff)
hdk: 234441648 sectors (120034 MB) w/2048KiB Cache, CHS=232581/16/63,
UDMA(33)
This is what you meant?
but after the boot I set hdparm manually for each drive with the following
settings:
hdparm -a8 -A1 -c1 -d1 -m16 -u1 /dev/hdc.
next prev parent reply other threads:[~2003-04-03 22:09 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-03 15:45 RAID 5 performance problems Jonathan Vardy
2003-04-03 15:45 ` Jonathan Vardy
2003-04-03 18:05 ` Peter L. Ashford
2003-04-03 18:05 ` Peter L. Ashford
2003-04-03 18:47 ` Ross Vandegrift
2003-04-03 19:22 ` Stephan van Hienen
2003-04-03 19:20 ` Stephan van Hienen
2003-04-03 19:28 ` Alan Cox
2003-04-03 21:02 ` Ezra Nugroho
2003-04-03 21:25 ` Stephan van Hienen
2003-04-03 21:38 ` Peter L. Ashford
2003-04-03 21:38 ` Peter L. Ashford
2003-04-03 22:09 ` Jonathan Vardy [this message]
2003-04-03 22:09 ` Jonathan Vardy
2003-04-03 22:16 ` Jonathan Vardy
2003-04-03 22:16 ` Jonathan Vardy
2003-04-03 22:28 ` Peter L. Ashford
2003-04-03 22:28 ` Peter L. Ashford
2003-04-03 21:42 ` Jonathan Vardy
2003-04-03 21:42 ` Jonathan Vardy
2003-04-03 22:13 ` Peter L. Ashford
2003-04-03 22:13 ` Peter L. Ashford
2003-04-04 20:39 ` H. Peter Anvin
2003-04-03 21:06 ` Felipe Alfaro Solana
2003-04-03 21:14 ` Jonathan Vardy
2003-04-03 21:14 ` Jonathan Vardy
-- strict thread matches above, loose matches on Subject: below --
2003-04-03 19:13 Neil Schemenauer
2003-04-03 19:49 Andy Arvai
2003-04-03 20:25 ` Mike Dresser
2003-04-03 20:25 ` Mike Dresser
2003-04-03 21:10 ` Jonathan Vardy
2003-04-03 21:10 ` Jonathan Vardy
2003-04-03 21:31 ` Ezra Nugroho
2003-04-03 20:10 Chuck Ebbert
2003-04-04 11:44 Jonathan Vardy
2003-04-04 11:44 ` Jonathan Vardy
2003-04-04 14:39 ` Ezra Nugroho
2003-04-04 15:05 Jonathan Vardy
2003-04-04 15:05 ` Jonathan Vardy
2003-04-04 16:01 Jonathan Vardy
2003-04-04 16:01 ` Jonathan Vardy
2003-04-05 0:10 ` Jonathan Vardy
2003-04-05 0:10 ` Jonathan Vardy
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='00bf01c2fa2d$afafedd0$2e77c23e@pentium4' \
--to=jonathanv@explainerdc.com \
--cc=ashford@sdsc.edu \
--cc=jonathan@explainerdc.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=raid@a2000.nu \
/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.