From: Ben DJ <bendj095124367913213465@gmail.com>
To: linux-raid@vger.kernel.org
Subject: Re: A few remaining questions about installing to RAID-10
Date: Fri, 2 Oct 2009 10:24:20 -0700 [thread overview]
Message-ID: <babafd2f0910021024m5fb72fc4k2304bf57e405f2fc@mail.gmail.com> (raw)
In-Reply-To: <20091002170156.GA21401@cthulhu.home.robinhill.me.uk>
Hi Robin,
On Fri, Oct 2, 2009 at 10:01 AM, Robin Hill <robin@robinhill.me.uk> wrote:
> Depends really - far isn't much slower on writes (the I/O elevator and
> filesystem buffering help). If you know /var will be write-mostly (it's
> often the default location for MySQL data files as well) then a near
> layout may be better though.
Ok, that's clear. /var is typically a mix, it seems. I may well
create a second set of partitions for read-write on /data & /var/cache
(I already put /tmp in tmpfs/RAM. /home I've mixed feeling about) --
once I've convinced myself that the benefits really show up in the
benchmarks. And decide whether it's worth the complexity. And, of
course, then the which FS to use decisions (would prefer ZFS, but n/a.
brtfs is promising but still experimental afaict. ext4 &/or xfs may
be my solutions); but that's for a different ML, I guess.
> RAID-1 over N disks can survive N-1 drive failures. Each disk holds a full copy of the data.
I really need to stop confusing RAID-0/1 mirrors & stripes. THanks.
> Currently only RAID-1,4,5 and 6 support growing arrays (by either adding
> spindles or increasing the capacity of each spindle). There are plans
> to add this capability to other RAID levels but I'm not sure where this
> sits on the priority list.
Good to know. With 4x1TB drives, I've got 2TB RAID-10 space to play
with. More than enough without worrying about the expansion too much.
For now.
Thanks.
Ben
--
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
next prev parent reply other threads:[~2009-10-02 17:24 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 [this message]
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
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=babafd2f0910021024m5fb72fc4k2304bf57e405f2fc@mail.gmail.com \
--to=bendj095124367913213465@gmail.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).