From: David Brown <david.brown@hesbynett.no>
To: Roy Sigurd Karlsbakk <roy@karlsbakk.net>
Cc: Piergiorgio Sartor <piergiorgio.sartor@nexgo.de>,
linux-raid@vger.kernel.org
Subject: Re: RAID-10 with mixed block size HDDs
Date: Fri, 29 Mar 2013 14:22:10 +0100 [thread overview]
Message-ID: <51559582.7000406@hesbynett.no> (raw)
In-Reply-To: <1036112.4.1364562908784.JavaMail.root@zimbra>
On 29/03/13 14:15, Roy Sigurd Karlsbakk wrote:
>>>> Hi all,
>>>>
>>>> I've a two disk RAID-10 (far 2, I guess).
>>>
>>> You can't grow a RAID-10…
>>
>> I know, I've to replace a disk, non add.
>
> I just don't understand why anyone would create a two-drive RAID-10,
> losing the flexibility of a mirror, and gaining nothing (since it's
> only on two drives)
>
With "far" layout, linux RAID-10 on two harddisks will give you the
safety of RAID-1 mirroring with /faster/ than RAID-0 speeds on reads.
(Writes are often a little slower than standard RAID-1 due to more head
movement, but slow writes can be buffered, while fast reads mean a
faster machine.)
Yes, you lose a bit of flexibility, and it would be very nice if RAID-10
could be re-shaped, grown, etc. But for a desktop system in particular,
RAID-10,far2 is the best you can get for two disks.
--
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
prev parent reply other threads:[~2013-03-29 13:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-25 18:04 RAID-10 with mixed block size HDDs Piergiorgio Sartor
2013-03-25 23:09 ` Chris Murphy
2013-03-26 19:05 ` Piergiorgio Sartor
2013-03-29 0:31 ` Roy Sigurd Karlsbakk
2013-03-29 9:04 ` Piergiorgio Sartor
2013-03-29 13:15 ` Roy Sigurd Karlsbakk
2013-03-29 13:22 ` David Brown [this message]
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=51559582.7000406@hesbynett.no \
--to=david.brown@hesbynett.no \
--cc=linux-raid@vger.kernel.org \
--cc=piergiorgio.sartor@nexgo.de \
--cc=roy@karlsbakk.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.