From: Mark Knecht <markknecht@gmail.com>
To: lrhorer@satx.rr.com
Cc: Linux-RAID <linux-raid@vger.kernel.org>
Subject: Re: Considering a complete rework of RAID on my home compute server
Date: Thu, 6 Jan 2011 10:17:28 -0800 [thread overview]
Message-ID: <AANLkTikxViM45MfjZvMCDAobeVVwBqMZHrm_Ws-bsAQt@mail.gmail.com> (raw)
In-Reply-To: <87.68.02631.5E6052D4@cdptpa-omtalb.mail.rr.com>
On Wed, Jan 5, 2011 at 4:03 PM, Leslie Rhorer <lrhorer@satx.rr.com> wrote:
>> 1) The Linux/MySQL stuff is a 3 drive RAID1. (sda/sdb/sdc)
>
> Well, RAID1 certainly offers the most robust solution, especially
> with more than 1 mirror.
>
<SNIP>
>
>> 3) There is a second RAID1 (sda/sdb/sdc) used for backups of the
>> RAID0. The RAID0 is backed up to RAID1 nightly. If the RAID0 fails
>> then I lose 1 day's work.
>
> Well, first of all, unless you meant to say sda1/sdb1/sdc1, etc,
> then this can't be different from the #1 RAID array above. Assuming you are
> actually using partitions, then I don't really see the value of two separate
> arrays. Why not just one RAID1 array?
>
Sorry I wasn't very clear.
In #1 the RAID1 is my main Linux system on sda3/sdb3/sdc3.
In #3 the RAID1 is purely for backups on /swa6/sdb6/sdc6 and is used
only for the backup of the RAID0 data. It is not normally mounted
except when doing backups. I wanted the extra protection that if
something went wrong with the basic Linux box the backup partition
would not normally be mounted and the data hopefully a bit safer.
> Also, I personally would reverse the backup strategy. I would put
> the Windows VM on the (single) main RAID array and back up the data to a
> single 1T hard drive.
>
I do this today backing up the existing RAID1 partitions to an
external eSATA 1TB drive.
>> OK - the problems I have with this arrangement are:
>>
>> 1) I used the older v0.9 metadata.
>
> This may be necessary if you are booting from the array. The
> limitations of the 0.90 superblock may never impact you. That's a small
> system with only a few drives.
>
>> 2) The RAIDs are assembled by the kernel automatically. I do not use
>> an initrd. (Because I don't know how/newer have)
>
> How is that a problem? An initrd, or lack thereof, won't prevent
> you from disabling the automatic assembly of one or more arrays, unless once
> again you boot from the array in question. Most modern distros default to
> using an initrd. What distro are you using?
>
The machines are Gentoo and an initrd/initramfs is up to the builder.
The new RAID6/superblock-1.2 boot uses one. The RAID1/superblock-0.9
does not.
>> 3) I think with 5 disks I could get better performance than I
>> currently get , with similar or better safety using maybe RAID5 or
>> RAID6.
>
> No, RAID1 is as safe as it gets. RAID0 allows for better
> performance, but if you make the RAID0 into your backup solution, the
> performance won't matter much.
>
If I'm wrong about RAID6 please correct me as this understanding is
why I chose it.
1) A 5-drive RAID6 can survive losing 2 disks and still return good data.
2) A 5-drive RAID6 reads data as nearly fast as a 3-drive RAID0.
If those two aren't true then my choice of RAID6 doesn't improve my
system as I hoped.
3) My current 3-drive RAID1 can lose 2 disks and still return good
data making #1 equivalent to #3
4) #2 would be faster than my current 2-drive RAID0 and wouldn't have
the risk of a single drive loss.
If #3 & #4 aren't correct then maybe RAID6 isn't buying me anything.
> Is performance a really big issue? Are you having problems with bad
> performance?
>
I think I am. On the current RAID0 side I'm running 4-5 Win XP VMs
doing number crunching. Each is sitting in a 20GB virtual disk which
is just files in VMWare or Virtualbox. Sometimes I run into moderate
periods of time (5-30 seconds) with disk activity lights flashing,
apparent loss of interactivity on the machine (mouse & keyboard not
responding quickly in Linux) even when the RAID1/Linux side isn't
doing anything. No cron jobs or anything like that running, just the
VMs sucking up CPU and disk. Most of the number crunching is reading
larger amounts of data, using the CPU and then writing some smallish
files out.
>> Overall, as I see it, I can suffer no disk loss on the RAID0, and
>> can handle a 2 disk loss on the RAID1. (Is that correct?) I'm thinking
>> that with a 5-drive RAID6 I might well get better performance than
>> either of the current RAIDs and (from reading) more protection during
>> a rebuild if one of my drives goes bad.
>
> A single RAID5 or RAID6 solution is certainly simpler, and there is
> significant value there. Read performance should be enhanced, but write
> performance will be impacted. You've also lost your backup solution in this
> scenario, though, so you will need to come up with something.
>
I have a local eSATA in my office and then a second machine in the
house with a 2-drive RAID1. I use them both for backups currently.
<SNIP>
>
> You might consider an external enclosure. Enclosures for up to 5
> dives are quite economical.
I will give it some thought.
Thanks!
- Mark
--
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:[~2011-01-06 18:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-29 19:54 Considering a complete rework of RAID on my home compute server Mark Knecht
2011-01-06 0:03 ` Leslie Rhorer
2011-01-06 0:47 ` Roman Mamedov
2011-01-06 2:05 ` Roberto Spadim
2011-01-06 10:45 ` Roman Mamedov
2011-01-06 8:10 ` Leslie Rhorer
2011-01-06 18:17 ` Mark Knecht [this message]
2011-01-06 23:57 ` John Robinson
2011-01-10 0:10 ` Leslie Rhorer
2011-01-10 1:45 ` Mark Knecht
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=AANLkTikxViM45MfjZvMCDAobeVVwBqMZHrm_Ws-bsAQt@mail.gmail.com \
--to=markknecht@gmail.com \
--cc=linux-raid@vger.kernel.org \
--cc=lrhorer@satx.rr.com \
/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).