linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: adfas asd <chimera_god@yahoo.com>
To: linux-raid@vger.kernel.org
Subject: Re: Remote NAS
Date: Wed, 23 Sep 2009 16:08:05 -0700 (PDT)	[thread overview]
Message-ID: <719154.37165.qm@web38805.mail.mud.yahoo.com> (raw)
In-Reply-To: <20090923200257.GA19027@cthulhu.home.robinhill.me.uk>

--- On Wed, 9/23/09, Robin Hill <robin@robinhill.me.uk> wrote:
> Obviously, but in the case of a RAID1 mirror, then this is
> immaterial
> (as either side of the mirror is identical), and in the
> RAID10 case it
> is controlled by the position of the drives in the array
> (which is
> controlled by the order they're given in the create
> statement).
> 
> > When I set up my NAS it's likely those remote drives
> will be sdc and
> > sdd (HTPC drives would be sda and sdb), so the RAID10
> create order
> > wouldn't help.
> > 
> Of course the create order helps - it's the _only_ way to
> control what
> chunks of the data go on which drive.  If your HTPC
> ends up with local
> drives sda and sdb, and remote drives sdc and sdd, then
> do:
> 
>     mdadm -C /dev/md0 -l 10 -p n2 -n 4 /dev/sda
> /dev/sdc /dev/sdb /dev/sdd
> 
> Then you'll end up with a RAID10 with all data held on both
> the sda/sdb
> and sdc/sdd pairs (so either pair can drop out of the array
> without
> losing any data).  The data layout will be:
> 
>     sda  sdb  sdc  sdd
>    
> A1   A2   A1   A2
>    
> A3   A4   A3   A4
>     ...
> 
> The equivalent happens for f2 or o2 arrays - though they're
> not strictly
> mirrored in those cases (they contain the same data but
> with a differing
> layout).
> 
> As I say though, this setup will still result in poor
> performance as you
> have the database and recordings on the same drives. 
> And to make them
> bootable you'd want to partition the drives first and
> create a separate
> 4-way RAID1 mirror for /boot.

YIKES, I'd better read this when I'm -not- drunk...

I take away that my main performance problem is in not separating by drive, the Myth database from the affected video.  Given these listserv transactions, I guess I have to resort to a 2.5" drive with the root filesystem and the Myth database, and the space-divided array for video storage.  I guess I can't RAID10 the root drive with the garage, as it might not be bootable, and you probably can't boot to a NAS drive anyway.   But this doesn't stop me from backing up the root drive onto the array.

It seems that I -can- control the role of the drives using your command above.  This is good news.

I will reexamine this tomorrow... 


      

       reply	other threads:[~2009-09-23 23:08 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20090923200257.GA19027@cthulhu.home.robinhill.me.uk>
2009-09-23 23:08 ` adfas asd [this message]
     [not found] <228497.14504.qm@web38801.mail.mud.yahoo.com>
2009-09-29 10:09 ` Remote NAS Leslie Rhorer
2009-09-22 19:38 adfas asd
2009-09-22 20:09 ` Robin Hill
2009-09-22 21:56   ` adfas asd
2009-09-23  7:57     ` Robin Hill
2009-09-23  9:13       ` Keld Jørn Simonsen
2009-09-23 14:59         ` adfas asd
2009-09-23 21:01           ` Keld Jørn Simonsen
2009-09-23 22:58             ` adfas asd
2009-09-23 14:52       ` adfas asd
2009-09-23 15:29         ` Robin Hill
2009-09-23 15:44           ` adfas asd
2009-09-23 16:10             ` Robin Hill
2009-09-27 20:19               ` Leslie Rhorer
2009-09-28 14:07                 ` adfas asd
2009-09-28 14:15                   ` Thomas Fjellstrom
2009-09-29 14:40                     ` adfas asd
2009-09-29  9:25                   ` Leslie Rhorer
2009-09-27 20:44           ` Leslie Rhorer
2009-09-27 22:00         ` Leslie Rhorer
2009-09-29 14:15           ` adfas asd
2009-09-30 15:36             ` Leslie Rhorer
  -- strict thread matches above, loose matches on Subject: below --
2009-09-16 16:21 adfas asd
2009-09-27 19:39 ` Leslie Rhorer
2009-09-27 20:09 ` 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=719154.37165.qm@web38805.mail.mud.yahoo.com \
    --to=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).