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: Tue, 22 Sep 2009 12:38:37 -0700 (PDT)	[thread overview]
Message-ID: <484423.6825.qm@web38807.mail.mud.yahoo.com> (raw)

No one has any idea on my questions?


--- On Wed, 9/16/09, adfas asd <chimera_god@yahoo.com> wrote:

> From: adfas asd <chimera_god@yahoo.com>
> Subject: Remote NAS
> To: linux-raid@vger.kernel.org
> Date: Wednesday, September 16, 2009, 9:21 AM
> A couple questions about MD RAID10:
> 
> Right now I'm RAIDing two 2TB drives in RAID10offset2. Need
> to add some drives and maybe I'll remote them using NAS (GB
> ethernet), for fire and theft protection.
>  
> So could the BIOS actually boot this if 2 drives are in the
> machine and 2 are in the garage? Is there a way to specify
> in mdadm that the two in the garage are mirrored from the
> two in the system?
> 
> Is GB ethernet NAS noticably slower than eSATA?  Is it
> reliable?
>  
> What if I use the mobo's e-SATA port to add 5 external
> drives locally. This would require a port multiplier. I
> presume it would not be bootable, since a port multiplier
> needs OS support? Or would something go in initrd.img? 
> Or would I need an individual boot drive to get things up?
>  
> Using the array to store MythTV recordings (very large
> files), but when it does commercial flagging (lots of
> writes) the array is so busy that GUI response is very
> slow.  I've set readahead cache to optimal (4096, after
> testing most sizes), so read should be OK.  I know far
> is optimized for read, so I chose offset in hopes it would
> bring up write speed.  Is there a way to speed up
> writes?
> 
> 
> 
>       
> 


      

             reply	other threads:[~2009-09-22 19:38 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-22 19:38 adfas asd [this message]
2009-09-22 20:09 ` Remote NAS 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
     [not found] <228497.14504.qm@web38801.mail.mud.yahoo.com>
2009-09-29 10:09 ` Leslie Rhorer
     [not found] <20090923200257.GA19027@cthulhu.home.robinhill.me.uk>
2009-09-23 23:08 ` adfas asd
  -- 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=484423.6825.qm@web38807.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).