From: Keld Simonsen <keld@keldix.com>
To: "Majed B." <majedb@gmail.com>
Cc: LinuxRaid <linux-raid@vger.kernel.org>
Subject: Re: RAID1 On 3 Drives
Date: Tue, 16 Mar 2010 02:46:00 +0100 [thread overview]
Message-ID: <20100316014600.GA25649@light.rap.dk> (raw)
In-Reply-To: <70ed7c3e1003150905x63605be5r6ee5874e60069e4b@mail.gmail.com>
On Mon, Mar 15, 2010 at 07:05:17PM +0300, Majed B. wrote:
> 100-200 MB is good enough for the /boot filesystem.
>
> How much swap to use depends on how much RAM you have and how much RAM
> the applications you use demand.
> If you have 4GB RAM or more, and most of your usage is about browsing
> the Internet, documents, watching videos, ..etc., then 2GB swap is
> more than enough even though I think you'll never use it.
> In case you ever need more than that, you could also create a
> swap-file -- whenever in need, create the file with the size you need
> on your array, activate the file as swap and that's it! When done with
> it, deactivated and delete the file to reclaim the capacity it once
> occupied.
>
> Personally, I keep my /home on its own partition. This guarantees that
> whatever system upgrades or distribution installs occur, /home won't
> be affected nor touched, and can be seen by multiple Linux distros if
> you're into multi-booting.
>
> I have a workstation with 4x 320GB disks with my root filesystem on it
> as RAID5. I have to say that it wasn't a good judgment going that way.
> One time one of the disks failed and the system refused to boot in
> degraded mode, so I had to boot from a CD, resync the array and then
> boot normally.
> That event got me thinking: Why don't I put / on its own disk and
> /home be on the RAID5 array. I could copy / to the array as a backup,
> should the OS disk crash; put a new disk, make it bootable, install
> grub on it, then using a LiveCD I could boot and access my RAID5 array
> and copy the OS files back.
>
> It's OK to have all disks running on the array without a spare. Just
> make sure you configure smartd and have it run tests on a daily basis
> (short tests) and a weekly basis (long tests) and to have it email you
> if problems occur.
>
> For RAID performance enhancements, the page seem to have been removed
> but a cached version of it is available:
> http://74.125.77.132/search?q=cache:5f7lyJQGL78J:www.linuxfoundation.org/collaborate/workgroups/linux-raid/performance+http://linux-raid.osdl.org/index.php/Performance&cd=1&hl=en&ct=clnk
Our wiki moved ... see
http://raid.wiki.kernel.org/index.php/Performance
>
> For RAID benchmarks:
> https://turing.phas.ubc.ca/mediawiki/index.php/RAID_benchmarks
does not involve Linux MD RAID. Linux MD RAID is generally faster then
HW RAID.
Best regards
keld
next prev parent reply other threads:[~2010-03-16 1:46 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-13 22:30 RAID1 On 3 Drives Joachim Otahal
2010-03-13 23:18 ` Carlos Mennens
2010-03-13 23:50 ` Bill Davidsen
2010-03-15 12:30 ` Carlos Mennens
2010-03-15 12:48 ` Majed B.
2010-03-15 14:47 ` Carlos Mennens
2010-03-15 16:05 ` Majed B.
2010-03-16 1:46 ` Keld Simonsen [this message]
2010-03-20 16:08 ` Bill Davidsen
-- strict thread matches above, loose matches on Subject: below --
2010-03-13 21:06 Carlos Mennens
2010-03-13 21:21 ` Majed B.
2010-03-13 21:24 ` Carlos Mennens
2010-03-14 21:09 ` Luca Berra
2010-03-13 21:45 ` Neil Brown
2010-03-13 21:26 ` Neil Brown
2010-03-13 21:31 ` Majed B.
2010-03-13 21:50 ` Neil Brown
2010-03-14 3:30 ` Majed B.
2010-03-14 1:22 ` thib
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=20100316014600.GA25649@light.rap.dk \
--to=keld@keldix.com \
--cc=linux-raid@vger.kernel.org \
--cc=majedb@gmail.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).