> 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.
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'...)
> Anyway since dmraid is assembling a raid you can't access sd{a,b}
> anymore and you need to look at what name the raid gets under
> /dev/mapper. I think it's dmraid0 but I could be wrong.
dmraid0 would be fine - thats the problem. It created a bl**dy stupid
/dev/mapper/nvidia_djeacebf
this time. /dev/mapper/nvidia0 would be more helpful and predictable
hence the original mail.
Once its up and I know the name I can install OK - well I hope so.
Plan is to create the separate domU disk chunks under LV's on the
mirror so I don't really care about accessing sda / sdb individually
That said I haven't pulled one of the drives yet to check that the
mirror stands up as it should.
(Wednedsdays fun n games...)
Andrew
|