From: "Keld Jørn Simonsen" <keld@dkuug.dk>
To: adfas asd <chimera_god@yahoo.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: A few remaining questions about installing to RAID-10
Date: Sat, 3 Oct 2009 18:55:34 +0200 [thread overview]
Message-ID: <20091003165534.GA19189@rap.rap.dk> (raw)
In-Reply-To: <275143.15844.qm@web38804.mail.mud.yahoo.com>
On Sat, Oct 03, 2009 at 07:12:55AM -0700, adfas asd wrote:
> --- On Fri, 10/2/09, Ben DJ <bendj095124367913213465@gmail.com> wrote:
> > On Fri, Oct 2, 2009 at 5:30 AM, adfas asd <chimera_god@yahoo.com>
> > wrote:
> >
> What I know is that 'offset' will boot and fail over. I don't know if 'far' will. I also know that .90 will boot and fail over. I don't know whether 1.x will. When building the array I tried to use 1.2 (as I thought it was newest/best) but there was a bitch at the beginning of boot and it wouldn't boot (for other reasons) so I reverted to .90. When I do it again I will likely use 1.0, given what I've recently learned here.
I am surprised that raid10,o2 will fail over. But maybe your bootloader
understands raidi10,o2. My understanding is that on the second copy of
the disk, blocks are flipped, and thus unreadable as a simple boot
device.
> I am still confused about the benefits of far vs offset. Keld (the developer) says that although offset is newer, it's not necessarily better than far, only more compatible. I have not found any rigorous performance comparisons of far vs offset.
I am not the developer of far, only the designer, and then I did a small patch.
There are a number of performance comparisons of far and offset at
http://linux-raid.osdl.org/index.php/Performance
If you are employing a filesystem, then be sure to look at tests
that also do so, to take advantage of the effects of the file system
elevator algorithms and buffering.
Best regards
keld
next prev parent reply other threads:[~2009-10-03 16:55 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-02 1:27 A few remaining questions about installing to RAID-10 Ben DJ
2009-10-02 2:31 ` Ben DJ
2009-10-02 3:16 ` Neil Brown
2009-10-02 3:46 ` Ben DJ
2009-10-02 12:30 ` adfas asd
2009-10-02 14:54 ` Ben DJ
2009-10-02 15:06 ` Keld Jørn Simonsen
2009-10-02 15:15 ` Robin Hill
2009-10-02 15:46 ` Ben DJ
2009-10-02 15:59 ` Robin Hill
2009-10-02 16:31 ` Ben DJ
2009-10-02 17:01 ` Robin Hill
2009-10-02 17:24 ` Ben DJ
2009-10-03 14:12 ` adfas asd
2009-10-03 16:55 ` Keld Jørn Simonsen [this message]
2009-10-03 17:02 ` Thomas Fjellstrom
2009-10-03 19:05 ` Drew
2009-10-03 21:09 ` adfas asd
2009-10-04 5:59 ` Thomas Fjellstrom
2009-10-05 4:59 ` Leslie Rhorer
2009-10-05 13:58 ` adfas asd
2009-10-02 7:51 ` Keld Jørn Simonsen
2009-10-02 7:54 ` Robin Hill
[not found] <20091005145711322.FNMG18886@cdptpa-omta02.mail.rr.com>
2009-10-05 15:30 ` adfas asd
2009-10-05 15:49 ` Drew
2009-10-05 15:55 ` adfas asd
2009-10-05 16:19 ` Drew
2009-10-05 18:13 ` Leslie Rhorer
2009-10-05 18:41 ` Drew
2009-10-06 0:50 ` Leslie Rhorer
2009-10-06 3:42 ` Drew
2009-10-06 9:11 ` Keld Jørn Simonsen
2009-10-06 13:24 ` adfas asd
2009-10-06 22:57 ` Ben DJ
2009-10-07 17:58 ` adfas asd
2009-10-25 5:20 ` Leslie Rhorer
2009-10-05 18:03 ` Leslie Rhorer
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=20091003165534.GA19189@rap.rap.dk \
--to=keld@dkuug.dk \
--cc=chimera_god@yahoo.com \
--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).