Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753906AbXLAMR6 (ORCPT ); Sat, 1 Dec 2007 07:17:58 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752564AbXLAMRm (ORCPT ); Sat, 1 Dec 2007 07:17:42 -0500 Received: from sovereign.computergmbh.de ([85.214.69.204]:39925 "EHLO sovereign.computergmbh.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752605AbXLAMRl (ORCPT ); Sat, 1 Dec 2007 07:17:41 -0500 Date: Sat, 1 Dec 2007 13:17:40 +0100 (CET) From: Jan Engelhardt To: Justin Piszcz cc: linux-kernel@vger.kernel.org, linux-raid@vger.kernel.org, apiszcz@solarrain.com Subject: Re: Kernel 2.6.23.9 + mdadm 2.6.2-2 + Auto rebuild RAID1? In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1105 Lines: 32 On Dec 1 2007 07:12, Justin Piszcz wrote: > On Sat, 1 Dec 2007, Jan Engelhardt wrote: >> On Dec 1 2007 06:19, Justin Piszcz wrote: >> >> > RAID1, 0.90.03 superblocks (in order to be compatible with LILO, if >> > you use 1.x superblocks with LILO you can't boot) >> >> Says who? (Don't use LILO ;-) > > I like LILO :) LILO cares much less about disk layout / filesystems than GRUB does, so I would have expected LILO to cope with all sorts of superblocks. OTOH I would suspect GRUB to only handle 0.90 and 1.0, where the MDSB is at the end of the disk <=> the filesystem SB is at the very beginning. >> > So two questions: >> > >> > 1) If it rebuilt by itself, how come it only rebuilt /dev/md0? >> >> So md1/md2 was NOT rebuilt? > > Correct. Well it should, after they are readded using -a. If they still don't, then perhaps another resync is in progress. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/