From: Matti Aarnio <matti.aarnio@zmailer.org>
To: "Loïc Paillotin" <loic.paillotin@qualimucho.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: i just read in the archive.........
Date: Fri, 14 Jun 2002 12:21:08 +0300 [thread overview]
Message-ID: <20020614122108.J19520@mea-ext.zmailer.org> (raw)
In-Reply-To: <1024044823.2250.15.camel@Asterix>; from loic.paillotin@qualimucho.com on Fri, Jun 14, 2002 at 10:53:43AM +0200
On Fri, Jun 14, 2002 at 10:53:43AM +0200, Loïc Paillotin wrote:
> I justy read in the archive that software raid would'nt work with ext3
> file system. Is that true ? ( i mean is that still true? )
RAID1 + EXT3 + SMP used to be a recipe for a deadlock, right now I am
not quite sure. I am running one SMP machine with IDE disks with
kernel 2.4.19-pre8smp and that hasn't groaked with saturation tests.
Hmm.. I am not sure that I have done saturation testing with that
new kernel either, but it contains a bunch of EXT3 fixes, which
might help.
What is definite is that RAID1 + EXT3 with UNIPROCESSOR KERNEL
(even if machine has multiple processors) does not deadlock.
So, if you are willing to run with uniprocessor kernel (effectively
to ditch additional CPUs at your SMP box), you will be safe.
If you want to test deadlocking (at a SMP machine with SMP kernel),
you can do it with:
dd if=/dev/zero bs=1024k of=test.file count=6000
Choose the count to be at least 2-3 times the amount of memory
in your machine.
If that doesn't deadlock, you are safe.
> --
> Loïc Paillotin
/Matti Aarnio
-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2002-06-14 9:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-14 8:53 i just read in the archive Loïc Paillotin
2002-06-14 9:21 ` Matti Aarnio [this message]
2002-06-14 10:00 ` Neil Brown
2002-06-14 10:56 ` Mark N.
2002-06-14 11:34 ` Luca Berra
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=20020614122108.J19520@mea-ext.zmailer.org \
--to=matti.aarnio@zmailer.org \
--cc=linux-raid@vger.kernel.org \
--cc=loic.paillotin@qualimucho.com \
/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