----- Original Message ----- From: "Marc" <linux-raid@xxxxxxxxxxxxxxxx> To: "JaniD++" <djani22@xxxxxxxxxxxxx>; <linux-raid@xxxxxxxxxxxxxxx> Sent: Thursday, January 05, 2006 7:16 AM Subject: Re: where is the spare drive? :-) > On Mon, 2 Jan 2006 00:26:58 +0100, JaniD++ wrote > > Hello, list, > > > > I found something interesting when i try to create a brand new array > > on brand new drives.... > > > > <snip> > > > 5. The question > > > > Why shows sdh2 as spare? > > The MD array size is correct. > > And i really can see, the all drive is reading, and sdh2 is *ONLY* writing. > > > > I'm not 100% sure but from a post by Neil a while a go on the list, the spare > device is a temporary construct created during the resync operation. Once the > resync is complete it should disappear. > > You could try searching the list archives for the post - choice of keywords is > up to you ;) Thanks, but i have found the bug already. ;-) If i create new raid5, it should only parity resyncing, and not spare rebuilding! This happens, only if i use mdadm. With raidtools works fine. My problem is now the bitmap. :( Only mdadm supports this.... Cheers, Janos > > Regards, > Marc > > - > To unsubscribe from this list: send the line "unsubscribe linux-raid" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html - To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
