From: Goswin von Brederlow <goswin-v-b@web.de>
To: Info@quantum-sci.net
Cc: linux-raid@vger.kernel.org
Subject: Re: RAID10 Layouts
Date: Fri, 21 Aug 2009 18:43:28 +0200 [thread overview]
Message-ID: <87ljldce33.fsf@frosties.localdomain> (raw)
In-Reply-To: <200908210627.06241.Info@quantum-sci.net> (Info@quantum-sci.net's message of "Fri, 21 Aug 2009 06:27:06 -0700")
Info@quantum-sci.net writes:
> Hello list,
>
> Researching RAID10, trying to learn the most advanced system for a 2
> SATA drive system. Have two WD 2TB drives for a media computer, and
> the most important requirement is data redundancy. I realize that
> RAID is no substitute for backups, but this is a backup for the
> backups and the purpose here is data safety. The secondary goal is
> speed enhancement. It appears that RAID10 can give both.
>
> First question is on layout of RAID10. In studying the man pages it
> seems that Far mode gives 95% of the speed of RAID0, but with
> increased seek for writes. And that Offset retains much of this
> benefit while increasing efficiency of writes. What should be the
> preference, Far or Offset? Are they equally as robust?
All raid10 layouts offer the same robustness. Which layout is best for
you really depends on your use case. Probably the biggest factor will
be the average file size. My experience is that with large files the
far copies do not cost noticeable write speed while being twice as
fast reading as raid1.
> How safe is the data in Far or Offset mode? If a drive fails, will
> a complete, usable, bootable system exist on the other drive?
> (These two are the only drives in the system, which is Debian
> Testing, Debian kernel 2.6.30-5) Need I make any special Grub
> settings?
I don't think lilo or grub1 can boot from raid10 at all with offset or
far copies. With near copies you are identical to a simple raid1 so
that would boot.
So to be bootable even with a failed drive you should partition the
disk. Create a small raid1 for the system and a large raid10 for the
data.
> What about this Intel firmware 'RAID'? Would this assist in any
> way? How does it relate (if it does) to the linux md system?
> Should I set in BIOS to RAID, or leave it at ACPI?
I would stay away from any half baked bios stuff. It will be no better
than linux software raid but will tie you to the specific bios. If
your mainboard fails and the next one has a different bios you can't
boot your disks.
> How does this look:
> # mdadm --create /dev/md0 --level=raid10 --layout=o2 --metadata=1.2 --chunk=64 --raid-disks=2 missing /dev/sdb1
On partitions it is save to use 1.1 format. Saves you 4k. Jupey.
You should play with the chunksize though and try with and without
bitmap and different bitmap sizes. Bitmap costs some write performance
but it greatly speeds up resyncs after a crash or temporary drive
failure.
MfG
Goswin
next prev parent reply other threads:[~2009-08-21 16:43 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-21 13:27 RAID10 Layouts Info
2009-08-21 16:43 ` Goswin von Brederlow [this message]
2009-08-21 18:02 ` Info
2009-08-21 19:20 ` Help Info
2009-08-21 19:38 ` Help John Robinson
2009-08-21 20:51 ` Help Info
2009-08-22 6:14 ` Help Info
2009-08-22 9:34 ` Help NeilBrown
2009-08-22 12:56 ` Help Info
2009-08-22 16:47 ` Help John Robinson
2009-08-22 18:12 ` Help Info
2009-08-22 20:45 ` Help Info
2009-08-22 20:59 ` Help Guy Watkins
[not found] ` <200908230631.46865.Info@quantum-sci.net>
2009-08-24 23:08 ` Help Info
2009-08-24 23:38 ` Help NeilBrown
2009-08-25 13:18 ` Help Info
2009-08-27 12:47 ` Help Info
2009-08-23 20:28 ` Help John Robinson
2009-08-22 6:31 ` RAID10 Layouts Goswin von Brederlow
2009-08-21 20:42 ` Keld Jørn Simonsen
2009-08-21 21:04 ` Info
2009-08-21 21:57 ` Bill Davidsen
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=87ljldce33.fsf@frosties.localdomain \
--to=goswin-v-b@web.de \
--cc=Info@quantum-sci.net \
--cc=linux-raid@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;
as well as URLs for NNTP newsgroup(s).