From: Francois Romieu <romieu@cogenit.fr>
To: "Peter H. R?egg" <pruegg@eproduction.ch>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Problem with mke2fs on huge RAID-partition
Date: Sat, 9 Feb 2002 20:57:34 +0100 [thread overview]
Message-ID: <20020209205734.A17825@fafner.intra.cogenit.fr> (raw)
In-Reply-To: <3C640C90.E71E3F70@eproduction.ch> <E16ZFbD-0004TM-00@the-village.bc.nu>
In-Reply-To: <E16ZFbD-0004TM-00@the-village.bc.nu>; from alan@lxorguk.ukuu.org.uk on Fri, Feb 08, 2002 at 06:18:15PM +0000
Alan Cox <alan@lxorguk.ukuu.org.uk> :
[...]
> The limit is about 1Tb currently. You are hitting something else, perhaps
> a driver or VM problem ?
Promise driver + 2.4.17, see:
Message-ID: <20020108003953.A16356@fafner.intra.cogenit.fr>
Message-ID: <20020119230852.A18674@se1.cogenit.fr>
| Intel | Promise
-----------------+-------+--------
raid1 creation | fast | fast
dd of=filesystem | fast | slow (*)
mkfs doesn't behaves too badly but it did when I first tried to raid1 the
whole disks.
Raid1 is software only.
As soon as a filesystem on the promise adapter comes into play, writes maxes
out at 2,5Mo/s. The previous machine (old PA2012 motherboard) with 8 times
less memory was able to stand 4~5Mo/s with vanilla broken kernel.
Now it's running 2.4.18-pre3-ac2 but the behavior is the same with vanilla
pre, vanilla + akpm ll, +ide patches. Feel free to ask if you want a test on a
specific version. I have dedicated a partition on each disk for testing.
--
Ueimor
next prev parent reply other threads:[~2002-02-09 19:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-08 17:36 Peter H. Rüegg
2002-02-08 17:47 ` Andreas Dilger
2002-02-08 18:18 ` Alan Cox
2002-02-09 19:57 ` Francois Romieu [this message]
2002-02-11 18:16 ` Bill Davidsen
2002-02-11 18:57 ` Francois Romieu
2002-02-11 20:57 ` Bill Davidsen
2002-02-12 9:10 ` Francois Romieu
2002-02-09 20:44 Rüegg, Peter H.
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=20020209205734.A17825@fafner.intra.cogenit.fr \
--to=romieu@cogenit.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=pruegg@eproduction.ch \
/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
all inboxes | Powered by JetHome®