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: A few remaining questions about installing to RAID-10
Date: Mon, 5 Oct 2009 06:58:54 -0700 (PDT)	[thread overview]
Message-ID: <427502.68563.qm@web38806.mail.mud.yahoo.com> (raw)
In-Reply-To: <20091005045942600.WUNS18886@cdptpa-omta02.mail.rr.com>



--- On Sun, 10/4/09, Leslie Rhorer <lrhorer@satx.rr.com> wrote:
> > I am
> working on putting / on a
> > dedicated high-performance 2.5" drive and keeping my
> videos on the array
> > as they're much too large to back up.
> 
>     You've said that before, but it is
> specious, as you are potentially
> using more space to mirror them on a RAID array than you
> would by
> implementing a backup array.  You don't have a
> separate backup, but they are
> using more space on your proposed system than they would be
> with my proposal
> for you.  I also rather expect in the long run it may
> be more of a
> management hassle for you.  It's your decision, of
> course.

I don't understand why you would say this.  Whether I set up a RAID1 in the garage and one in the house and RAID0 them, or just set up a RAID10, it should not have any impact on the space.  And more arrays means -more- management hassle, not less. 

And I don't understand how you can set up an array without partitions?  Do you then LVM it and partition -that-? Is that actually possible?

 


      

  reply	other threads:[~2009-10-05 13:58 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
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 [this message]
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=427502.68563.qm@web38806.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).