From: NeilBrown <neilb@suse.de>
To: Seblu <seblu@seblu.net>
Cc: linux-raid@vger.kernel.org
Subject: Re: Mdadm, udev and fakeraid?
Date: Tue, 5 Apr 2011 16:20:08 +1000 [thread overview]
Message-ID: <20110405162008.5f2c48fe@notabene.brown> (raw)
In-Reply-To: <BANLkTinp3376PV3sJWARXtFnRfoMsg44wA@mail.gmail.com>
On Sun, 3 Apr 2011 18:03:50 +0200 Seblu <seblu@seblu.net> wrote:
> Hello,
>
> In the following commit, udev rules load isw_raid (fakeraid). From my
> test, this doesnt work. I have to call dmraid to have something
> working.
> http://neil.brown.name/git?p=mdadm;a=commit;h=475a01b8bce8575dd1b2ab6495e65e854702ac0e
>
> isw_raid is only fakeraid devices? mdadm is able to mount fakeraid partition?
>
I'm sorry but I cannot parse those questions successfully so I'm not sure
what you are asking.
Both dmraid and mdadm can manage some 'fakeraid' arrays. dmraid supports a
wider variety. mdadm supports raid1 and raid5 more completely than dmraid
does.
Both should support isw to some degree.
Intel are currently working with mdadm to make it provide full support for
"IMSM" (Intel Matrix Storage Manager). I don't know the exact relationship
between 'isw' and 'IMSM' - maybe they are different names for the same thing.
If mdadm doesn't work for your isw arrays, and you want it to, then I suggest
you report details about what is, or is not, happening.
Useful information would include:
mdadm --examine /dev/DEVICE
for each device in the array.
Also the output of
mdadm --incremental --verbose /dev/DEVICE
for each device in turn. This should incrementally assemble the array from
all those components.
NeilBrown
next prev parent reply other threads:[~2011-04-05 6:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-03 16:03 Mdadm, udev and fakeraid? Seblu
2011-04-05 6:20 ` NeilBrown [this message]
2011-04-15 14:15 ` Seblu
2011-04-16 5:27 ` Luca Berra
2011-04-18 0:38 ` NeilBrown
2011-04-22 11:24 ` Seblu
2011-04-23 2:37 ` Dan Williams
2011-04-23 8:45 ` NeilBrown
2011-04-26 6:06 ` Luca Berra
2011-04-24 22:44 ` Seblu
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=20110405162008.5f2c48fe@notabene.brown \
--to=neilb@suse.de \
--cc=linux-raid@vger.kernel.org \
--cc=seblu@seblu.net \
/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).