On Sun, Jun 01, 2008 at 08:38:01PM +0100, Andrew Elwell wrote:
> > Why are you trying to use dmraid instead of the md one? It's not like
> > you get any better performance or reliability quite the opposite in
> > fact.
>
> uh, because thats what SL5x does by default if you say "remove all
> data on the disks and create the default" - I let it do its own thing
> to see what it tried. This was considered a test rather than the final
> production method.
It's not the default, dmraid only fires up if it detects that the disks
have relevant metadata (most likely someone created a mirror on the bios
or from windows). Unless I am mistaken dmraid still isn't close to what
md can offer (rebuilds are only available from the bios menu, no way to
do scrubs or even to monitor the array) it's only there to let you
access raid sets that you had under windows and it's not recommended for
"real" use.
Just do a dmraid -E -r /dev/sdX or whatever the right command is to wipe
the fakeraid[1], reboot and you'll never see it again. Booting the
installer with nodmraid will also prevent it from starting up and allow
you to do an normal install with md (since the metadata will be wiped
out it's not needed afterwards).
> I've no objection to the dm stuff over md as thats what I've been used
> to in the past with multipath SAN connections (shudder qlogic - I'm
> almost through the rehab and thinking that 'maybe iscsi's not so bad
> after all'...)
dm-multipath is quite a different beast than dmraid if you are talking
about it.
Cheers,
Kostas
[1] http://linuxmafia.com/faq/Hardware/sata.html#fakeraid
|