linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Keld Jørn Simonsen" <keld@dkuug.dk>
To: Maxime Boissonneault <maxime.boissonneault@usherbrooke.ca>
Cc: Bill Davidsen <davidsen@tmr.com>,
	robin@robinhill.me.uk, linux-raid@vger.kernel.org
Subject: Re: Upgrading a software RAID
Date: Sun, 31 May 2009 02:17:30 +0200	[thread overview]
Message-ID: <20090531001730.GA16311@rap.rap.dk> (raw)
In-Reply-To: <4A217C6C.7080301@usherbrooke.ca>

On Sat, May 30, 2009 at 02:35:24PM -0400, Maxime Boissonneault wrote:
>
>>>
>>> I can not install more drives in the computer. It is a home theater  
>>> computer in a small case. I was expecting to be able to let the raid  
>>> manage the copies itself.
>>>
>>> If the / was on a RAID5, would it be able to boot with 2 disks ?
>>> If so, is it possible to convert my RAID0 to a RAID5 ?
>>> For example, I could boot on a CD, backup / onto /home, delete the  
>>> RAID0 array and recreate it as RAID5, then restore the backup. Would  
>>> this work ?
>>
>> Based on my testing (somewhat old now) and regular use, I would say  
>> raid10 is probably your best bet. It's fast and secure, and with the  
>> -f2 option for "far" copies it's able to give high transfer rates.
>
> Doesn't RAID10 means RAID 1+0, which requires 4 disks ?

Linux RAID10 is somewhat different from raid1+0, and can run with just 2
disks, with fine performance for reads in the F2 layout, almost raid0
performance, while write performance is close to raid1, with a file system in operation.

Best regards
keld

  parent reply	other threads:[~2009-05-31  0:17 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-25 15:32 Adaptec 2405 : hardware or software raid? Janek Kozicki
2009-05-25 16:52 ` Andrew Burgess
2009-05-25 17:05   ` Upgrading a software RAID Maxime Boissonneault
2009-05-28 13:38     ` Bill Davidsen
2009-05-28 13:44       ` Maxime Boissonneault
2009-05-28 14:05         ` Bill Davidsen
2009-05-28 14:14     ` Robin Hill
2009-05-28 14:32       ` Maxime Boissonneault
2009-05-28 15:08         ` Robin Hill
2009-05-30 18:11           ` Maxime Boissonneault
2009-05-30 19:03             ` Robin Hill
2009-05-30 20:03               ` Maxime Boissonneault
2009-05-30 20:15                 ` Robin Hill
2009-05-30 22:18                   ` Maxime Boissonneault
2009-05-30 22:52                     ` Maxime Boissonneault
2009-06-02 18:23                     ` Bill Davidsen
2009-06-02 18:32                       ` Thomas Fjellstrom
2009-06-02 19:57                         ` Bill Davidsen
2009-06-02 20:03                           ` Thomas Fjellstrom
2009-06-02 21:13                           ` CoolCold
2009-06-03 16:30                             ` Bill Davidsen
2009-05-29  8:58         ` Keld Jørn Simonsen
2009-05-30 18:32         ` Bill Davidsen
2009-05-30 18:35           ` Maxime Boissonneault
2009-05-30 19:10             ` Robin Hill
2009-05-30 22:39             ` Bill Davidsen
2009-05-31  0:17             ` Keld Jørn Simonsen [this message]
2009-05-31  5:21               ` Maxime Boissonneault
2009-06-02 18:33                 ` 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=20090531001730.GA16311@rap.rap.dk \
    --to=keld@dkuug.dk \
    --cc=davidsen@tmr.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=maxime.boissonneault@usherbrooke.ca \
    --cc=robin@robinhill.me.uk \
    /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).