linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* Order of kernel autodetect
@ 2005-04-17  6:21 TJ
  2005-04-20 15:58 ` Derek Piper
  0 siblings, 1 reply; 2+ messages in thread
From: TJ @ 2005-04-17  6:21 UTC (permalink / raw)
  To: linux-raid

I searched through the mailing list archive but I can not find this. I 
remember a discussion about trouble being caused from lack of control of the 
order that kernel autodetect chooses, and a patch to be able to control it. 
I'm running an array on top of another array right now, a RAID 5 on a linear. 
I understand the consequences of this, it's temporary. Still, the kernel 
tries to bring up the RAID 5 array before the linear, so the linear array is 
not included. If there is no way to correct this in the kernel, I need some 
help on understanding how init.rd level raid starting is supposed to work. It 
must happen very early, obviously, to ensure that auto-fsck works correctly. 
I'm guessing that it should be first, or close to first in the scripts. The 
general idea would be simply to run mdadm from a script to start the arrays, 
then? 

Thanks
TJ

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2005-04-20 15:58 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2005-04-17  6:21 Order of kernel autodetect TJ
2005-04-20 15:58 ` Derek Piper

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).