tech-kern archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: RAIDframe nested autoconfiguration

der Mouse <mouse%Rodents-Montreal.ORG@localhost> writes:

> In passing, is there a way to boot with raid autoconfiguration
> suppressed?

One might think that booting with -c and doing "disable raid" or
"disable raid0" at the userconf(4) prompt would do something, and one
would be wrong.  This should probably be fixed.

> Hmm.  raid0 = sd0e, sd1e, missing; raid1 = sd2e, sd3e, raid0e; can
> raid1e then fill out the missing member of raid0?

No, my changes don't try to fill in missing components of a RAID set
that's already been brought up; instead, I put off configuring any
degraded RAID sets until bringing up complete RAID sets can make no more

This, incidentally, means that in cases like the above (assuming the two
sets are both RAID-5), both raid0 and raid1 will be brought up in
degraded mode, and the administrator will have to intervene once the
system is up; but, if the "missing" disk in raid0 were present, then
everything would work.  (I considered having the kernel try to guess
which set to configure first in cases like that, but it seemed a bad
idea.)  This is also the cause of the mirror-splitting problem I've
described in a separate message.

(let ((C call-with-current-continuation)) (apply (lambda (x y) (x y)) (map
((lambda (r) ((C C) (lambda (s) (r (lambda l (apply (s s) l))))))  (lambda
(f) (lambda (l) (if (null? l) C (lambda (k) (display (car l)) ((f (cdr l))
(C k)))))))    '((#\J #\d #\D #\v #\s) (#\e #\space #\a #\i #\newline)))))

Home | Main Index | Thread Index | Old Index