From: Turbo Fredriksson <turbo@bayour.com>
To: linux-raid@vger.kernel.org
Subject: Re: linux-raid compatable w/ Adaptec AIC-7902?
Date: Fri, 08 Jul 2005 14:40:22 +0200 [thread overview]
Message-ID: <877jg1fp3d.fsf@pumba.bayour.com> (raw)
In-Reply-To: <200507071149.54019.eric@pretorious.net> (Eric Pretorious's message of "Thu, 7 Jul 2005 11:49:53 -0700")
Quoting Eric Pretorious <eric@pretorious.net>:
> On Monday 04 July 2005 04:27 am, Turbo Fredriksson wrote:
>>WHY are you putting multiple md's on the same disks? Did you intend to
>>do something like this?
>>
>> md0 /boot sd[ab]1
>> md1 / sd[ab]2
>> md2 /usr sd[ab]3
>> md3 /var sd[ab]4
>>
>>Just one question (this is the magic :). What do you gain by this? And
>>why do you do it?
>
> I'm just trying to mirror two disks - that's all. Is there a better way?
The keyword(s) here is _same disk_.
This is a very complicated way to do it... The idea behind partitioning the
disk(s) this way (many partition, one partition for 'each important FS') is
'to protect the root partition' (or rather 'protect the file systems from
each others failures'). That is, a crash in the /var FS (or that partition)
will not interfere against the /usr FS/partition etc...
This is almost a must to have ANY kind of security against data loss, but
but why do RAID; to protect the FS from hardrive failures...
This two ways of thinking is kinda the same thing, so why do all the
partitioning if one uses RAID?!
Just create ONE partition (plus a swap on each disk, totaling the total amount
of swap you want/need) and set that up as md0 (mounted as /) and that's it!
If a disk/partition crashes, then the RAID 'system' will kick in. If you're
mirroring the disks that is. It won't work if you'r joining disks to get more
space, which is quite pointless in the first place nowadays. Harddisks are so
cheap so just buy a bigger one...
In theory, the way you do it (and the way I used to to it previosly) way will
save you from filesystem (not hardware related!) crashes, but i haven't seen
a filesystem crash in years (ext[23] etc is getting _quite_ stable these days),
but even if the FS crashes the RAID should still kick in to save you data...
This is the way I'm reasoning at least. I might have missed something, and if
I have, I'm interessted in hearing why...
The weak point in my reasoning is if the RAID really saves you from _filesystem_
crashes... I think it does, but I'm not sure...
--
KGB Saddam Hussein Nazi toluene cracking NORAD ammunition Ft. Bragg
arrangements Cuba Peking FSF AK-47 Waco, Texas Soviet
[See http://www.aclu.org/echelonwatch/index.html for more about this]
next prev parent reply other threads:[~2005-07-08 12:40 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-29 22:38 linux-raid compatable w/ Adaptec AIC-7902? Eric Pretorious
2005-06-29 22:57 ` Eric Pretorious
2005-06-29 23:57 ` Eric Pretorious
2005-06-29 23:55 ` Eric Pretorious
2005-06-30 2:10 ` Guy
2005-06-30 17:14 ` Eric Pretorious
2005-07-04 11:27 ` Turbo Fredriksson
2005-07-07 18:49 ` Eric Pretorious
2005-07-08 0:35 ` Mathieu Chouquet-Stringer
2005-07-08 12:40 ` Turbo Fredriksson [this message]
2005-07-08 12:52 ` Joshua Baker-LePain
2005-07-08 22:56 ` Mark Hahn
2005-07-08 23:20 ` Tyler
2005-06-30 0:38 ` Eric Pretorious
2005-06-30 1:08 ` Eric Pretorious
2005-06-30 15:51 ` Dinesh
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=877jg1fp3d.fsf@pumba.bayour.com \
--to=turbo@bayour.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).