From: Volker Armin Hemmann <volker.armin.hemmann@tu-clausthal.de>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Is an Intel motherboard RAID better or worse than software RAID?
Date: Mon, 20 Oct 2008 13:24:11 +0200 [thread overview]
Message-ID: <200810201324.11273.volker.armin.hemmann@tu-clausthal.de> (raw)
In-Reply-To: <20081020031346.4a2c753a@mandalor.homelinux.net>
On Montag 20 Oktober 2008, Conway S. Smith wrote:
> On Mon, 20 Oct 2008 08:54:20 +0200
>
> Wolfgang Liebich <Wolfgang.Liebich@siemens.com> wrote:
> > Hi,
> >
> > <SNIP>
> >
> > > the howtos on gentoo-wiki worked well for me.
> >
> > I'm working with them, too. Just one question remains: I want to use
> > udev. Do I have to create the md devices or does udev that for me?
>
> udev will do it for you. But make sure your initramfs init script
> unmounts /sys & /proc.
just don't use an initramfs/initrd.
> > Sorry, I'm neither a LVM nor a RAID export - could you please
> > elaborate on that?
> > I like LVM because of the convenience it adds.
>
> Write barriers are a feature to allow write caching on the hard disks
> w/out endangering filesystem integrity. Write caching helps
> performance significantly, but also allows the disk to re-order write
> requests - the disk may actually write a write-request that was
> received later before a write-request that was received earlier,
> which in some situations can lead to filesystem corruption. Write
> barriers are a special type of request that the disk is not allowed
> to reorder around - everything the disk receives before the write
> barrier must be written before anything received after the write
> barrier. But in order to work, write barriers need to be supported
> by every layer from the filesystem down to the actual disk; if your
> filesystem is on top of LVM & LVM doesn't support write barriers,
> then you won't be able to use them, and if write caching is enabled
> on the actual disks, you may be risking fileystem corruption. The
> Device Mapper kernel subsystem (dm-crypt, dm-raid, LVM, etc.) does
> not support write barriers - but neither does MD RAID except for
> RAID1, so write caching is dangerous except for filesystems directly
> on disk partitions or on RAID1 (if the RAID1 is directly on disk
> partitions).
also, reiserfs and xfs turn barriers on by default, ext3 turns it off per
default. Because of 'performance reasons'.
next prev parent reply other threads:[~2008-10-20 11:24 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-15 13:08 [gentoo-user] Is an Intel motherboard RAID better or worse than software RAID? Wolfgang Liebich
2008-10-15 13:13 ` Pintér Tibor
2008-10-15 13:22 ` Alan McKinnon
2008-10-17 10:40 ` Wolfgang Liebich
2008-10-17 11:31 ` Neil Bothwick
2008-10-17 11:43 ` Volker Armin Hemmann
2008-10-18 16:54 ` Peter Humphrey
2008-10-20 6:54 ` Wolfgang Liebich
2008-10-20 9:13 ` Conway S. Smith
2008-10-20 11:24 ` Volker Armin Hemmann [this message]
2008-10-20 13:31 ` Conway S. Smith
2008-10-20 15:33 ` Volker Armin Hemmann
2008-10-21 8:59 ` Peter Humphrey
2008-10-21 18:04 ` Liebich, Wolfgang
2008-10-18 5:31 ` jormaa
2008-10-15 13:24 ` Dirk Heinrichs
2008-10-23 7:18 ` AW: " Liebich, Wolfgang
2008-10-15 13:34 ` Albert Hopkins
2008-10-15 13:41 ` Pintér Tibor
2008-10-15 14:45 ` Dan Cowsill
2008-10-15 16:48 ` Volker Armin Hemmann
2008-10-16 19:42 ` Paul Hartman
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=200810201324.11273.volker.armin.hemmann@tu-clausthal.de \
--to=volker.armin.hemmann@tu-clausthal.de \
--cc=gentoo-user@lists.gentoo.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