From: gauravmahajan2007@gmail.com (Gaurav Mahajan)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Regarding Raid1
Date: Thu, 23 Dec 2010 18:55:06 +0530 [thread overview]
Message-ID: <AANLkTikXg8ab1FvR_vApZTjaZY+yuN+z_NCW6EikzL5O@mail.gmail.com> (raw)
In-Reply-To: <AANLkTimV+mCAuBeYwbETQ7rw+3gBDUsQ+Kuu4wjpFaHG@mail.gmail.com>
Hi Greg...
Thanks for the valuable info...
I tried to understand a few more concepts.....
I believe that md raid is a software raid,which makes it OS dependent
whereas dmraid can be used to create a hardware raid (fakeRAID) which
is OS independent...
Now, what I fail to understand is that whether mdadm, which is a
software tool for creating software RAID uses device mapper
functionality or not. For example, lets say I create a RAID 1 array
using mdadm, will the read and write operations performed on this
array be passed through the device mapper or is the device mapper
bypassed in this case ? The fact that the device mapper is supposed to
be the lowest layer in the storage stack is what brought this question
to my mind....
Basically, I'm wondering whether md and dm are at the same level or is
dm at the lower level and md at a higher level....
It would be really helpful if you could elaborate on the difference
between the working of md and dm....
Regards,
Gaurav
On Sun, Dec 19, 2010 at 10:48 AM, Mulyadi Santosa
<mulyadi.santosa@gmail.com> wrote:
> Hi Greg.......
>
> On Sun, Dec 19, 2010 at 07:28, Greg Freemyer <greg.freemyer@gmail.com> wrote:
>> Both Raid 10 and Raid 1+0 effectively mean the same.
>>
>> The plus is basically implied unless you want Raid 0+1. ?I've never
>> seen that call raid 01.
>>
>> I think the use varies on how you build the array. ?If you first build
>> a stripeset, then mirror them as 2 separate steps, then use 1+0.
>>
>> If on the otherhand you make a single call to mdadm (as an example)
>> and tell it do do the work in one step, then it is raid 10. ?The
>> advantage of raid 10 over 1+0 is mdadm has several ways internally to
>> build a raid 10 whereas there is basically only one way to build a
>> 1+0..
>
> Thanks for your kind explanation....I'll dig further about it when I
> have time. I never knew 'til this you explained it to me that mdadm
> might have its own way to build 1+0...I always think it always be:
> build mirror, then stripe them....
>
> --
> regards,
>
> Mulyadi Santosa
> Freelance Linux trainer and consultant
>
> blog: the-hydra.blogspot.com
> training: mulyaditraining.blogspot.com
>
next parent reply other threads:[~2010-12-23 13:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AANLkTi=F-ceJBnfVERXUCY859ByX1QyG4G-+WE74PKy2@mail.gmail.com>
[not found] ` <AANLkTimQO4aa6kTtM6kLsETfsNiARxenFohRRQk_-=-Z@mail.gmail.com>
[not found] ` <AANLkTi=yqLEDYXXMe9F5a+usyCSAfRhJN7tMeU2OsOX4@mail.gmail.com>
[not found] ` <AANLkTimM5Zvpoj-XtKQchujgHHk_jWmY8wEQQ7RewV78@mail.gmail.com>
[not found] ` <AANLkTikWPYDyVS=w6n6FHSfOqK61yk9htwi66hfeb+rQ@mail.gmail.com>
[not found] ` <AANLkTimV+mCAuBeYwbETQ7rw+3gBDUsQ+Kuu4wjpFaHG@mail.gmail.com>
2010-12-23 13:25 ` Gaurav Mahajan [this message]
2010-12-23 23:12 ` Regarding Raid1 Greg Freemyer
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=AANLkTikXg8ab1FvR_vApZTjaZY+yuN+z_NCW6EikzL5O@mail.gmail.com \
--to=gauravmahajan2007@gmail.com \
--cc=kernelnewbies@lists.kernelnewbies.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).