From: "Jeff V. Merkey" <jmerkey@utah-nac.org>
To: Alex Bligh - linux-kernel <linux-kernel@alex.org.uk>
Cc: Florian Weimer <fw@deneb.enyo.de>,
Lawrence Walton <lawrence@the-penguin.otak.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: 3ware 9550SX problems - mke2fs incredibly slow writing last third of inode tables
Date: Tue, 01 Nov 2005 15:54:30 -0700 [thread overview]
Message-ID: <4367F226.4040302@utah-nac.org> (raw)
In-Reply-To: <B4CA35A2CFBAF97FCE2856B0@[192.168.100.25]>
I see this problem if you have the array configured for RAID 5 and you
have not pushed the F8 key during array config after setting up
the array. Try rebooting, setting the Raid 5 for INIT (Press F8) and it
goes away, but the whole array will reinit itself. There seems to be
some sort of problem in their RAID 5 logic and you can setup a RAID 5
stripe set, but init doesn't finish or gets in a wierd state during
reboot. It seems confined to 9500 series controllers, but I have also
seen this behavior on the 8000 series drivers as well. I don't know
if you are using RAID 5 , but I have seen this problem on RAID 5 configs
only.
Jeff
Alex Bligh - linux-kernel wrote:
>
>
> --On 01 November 2005 18:13 +0100 Florian Weimer <fw@deneb.enyo.de>
> wrote:
>
>>>> In my experience, the 3ware SATA controllers which are not NCQ-capable
>>>> have very, very lousy write performance with some drives, unless you
>>>> enable the write cache (which is, of course, a bit dangerous without
>>>> UPS or battery backup on the controller).
>>>
>>
>>> Not to sound like the a 3ware chearleader, but this card does support
>>> NCQ.
>>
>>
>> Oh. I didn't know whether this particukar controller supported NCQ or
>> not.
>
>
> It even supports SATA-3, not much good that it does me.
>
> I managed to format it reiserfs in the end. dbench (yes I know it isn't a
> great benchmark) gives me a write speed of 7Mb/s compared to 700Mb/s
> if one
> of the disks in the array is attached to the motherboard SATA controller.
>
> 7Mb/s is quite stunningly appalling. I realise the release notes warn of
> slow writes, but that's just daft! I have a few bits in my setup to check
> before I start pointing the finger comprehensively. It may (for instance)
> be a large partition problem (suggested on the ext2 list).
>
> I'm taking it that it works at least for some people (did you test write
> speed Lawrence?).
>
> --
> 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-02 0:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-30 21:10 3ware 9550SX problems - mke2fs incredibly slow writing last third of inode tables 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 [this message]
2005-11-02 22:39 ` Alex Bligh - linux-kernel
[not found] <BEDEA151E8B1D6CEDD295442@192.168.100.25>
2005-11-02 22:59 ` adam radford
2005-11-05 9:06 ` Alex Bligh - linux-kernel
2005-11-05 17:01 ` Jeff V. Merkey
2005-11-07 21:53 ` Florian Weimer
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=4367F226.4040302@utah-nac.org \
--to=jmerkey@utah-nac.org \
--cc=fw@deneb.enyo.de \
--cc=lawrence@the-penguin.otak.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