From: "Jeff V. Merkey" <jmerkey@wolfmountaingroup.com>
To: Alex Bligh - linux-kernel <linux-kernel@alex.org.uk>
Cc: adam radford <aradford@gmail.com>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: 3ware 9550SX problems - mke2fs incredibly slow writing last third of inode tables
Date: Sat, 05 Nov 2005 10:01:37 -0700 [thread overview]
Message-ID: <436CE571.5020801@wolfmountaingroup.com> (raw)
In-Reply-To: <98C5049497A78ECC77D350B7@[192.168.100.25]>
Alex Bligh - linux-kernel wrote:
> Adam,
>
>>> All seems to go well until I try and do mke2fs. This appears to work,
>>> and tries to write the inode tables. However, at (about) 3400 inodes
>>> (of 11176), it slows to a crawl, writing one table every 10 seconds.
>>> strace shows it is still running, and no errors are being reported.
>>> However, it seems very sick.
>>
>>
>> Do you have cache turned on or off? If it's off, try turning it on.
>
>
> On. I started again (deleted the units etc.) which I'd done before.
> I am not sure quite what I did different this time. Now I get 270Mb/s
> on dbench, 100Mb/s (approx) on a solid contiguous write (dd), which
> is well into the field of uninspiring but not as daft as 7Mb/s. I had
> rather expected that h/w RAID 5 would give me faster reads, and only
> slightly degraded writes, compared to a single disk of the same type
> plugged into the motherboard SATA.
>
> However, dbench puts the (dual opteron 275) machine into 99% system
> state. Is that normal? Surely it should be in i/o wait.
>
> I /think/ what had happened is this: When I press F8 to exit the
> BIOS, it did not initialize the array (this is in accordance with the
> manual, it being deferred). Despite leaving the machine idle in the O/S
> for 2 days, it didn't start initializing the array. Running the mkfs
> started the initialization (would that make sense)? The second time
> I ran mkfs, I may have already (somehow) triggered it to start earlier.
>
> I shall try and work out some soak test I can run on it this w/e.
This is what I reported earlier and is the same behavior I am seeing on
he 9500. I don't think its related
to the firmwae, but something in the driver because I can reproduce it
on 8000 series controllers as well.
What's common between the two is it's on a 2.6.9 kernel with the
drivers. Eventually, the init proceeds
and completes, but it's related to the INIT state not getting tripped
into running.
Jeff
>
> --
> Alex Bligh
> -
> To unsubscribe from this list: send the line "unsubscribe
> linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
next prev parent reply other threads:[~2005-11-05 17:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <BEDEA151E8B1D6CEDD295442@192.168.100.25>
2005-11-02 22:59 ` 3ware 9550SX problems - mke2fs incredibly slow writing last third of inode tables adam radford
2005-11-05 9:06 ` Alex Bligh - linux-kernel
2005-11-05 17:01 ` Jeff V. Merkey [this message]
2005-11-07 21:53 ` Florian Weimer
2005-10-30 21:10 Alex Bligh - linux-kernel
2005-11-01 12:45 ` Florian Weimer
2005-11-01 17:04 ` Lawrence Walton
2005-11-01 17:13 ` Florian Weimer
2005-11-02 0:11 ` Alex Bligh - linux-kernel
2005-11-01 22:54 ` Jeff V. Merkey
2005-11-02 22:39 ` Alex Bligh - linux-kernel
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=436CE571.5020801@wolfmountaingroup.com \
--to=jmerkey@wolfmountaingroup.com \
--cc=aradford@gmail.com \
--cc=linux-kernel@alex.org.uk \
--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