From: Justin Piszcz <jpiszcz@lucidpixels.com>
To: Jan Engelhardt <jengelh@computergmbh.de>
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?
Date: Sat, 1 Dec 2007 07:22:57 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.4.64.0712010722460.28887@p34.internal.lan> (raw)
In-Reply-To: <Pine.LNX.4.64.0712011313490.30316@fbirervta.pbzchgretzou.qr>
On Sat, 1 Dec 2007, Jan Engelhardt wrote:
>
> 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.
>
There was nothing in progress, md0 was synced up and md1,md2 = degraded.
next prev parent reply other threads:[~2007-12-01 12:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-01 11:19 Justin Piszcz
2007-12-01 12:10 ` Jan Engelhardt
2007-12-01 12:12 ` Justin Piszcz
2007-12-01 12:17 ` Jan Engelhardt
2007-12-01 12:22 ` Justin Piszcz [this message]
2007-12-05 19:29 ` Nix
2007-12-06 15:08 ` Jan Engelhardt
2007-12-07 7:30 ` Nix
2007-12-07 8:36 ` Jan Engelhardt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.64.0712010722460.28887@p34.internal.lan \
--to=jpiszcz@lucidpixels.com \
--cc=apiszcz@solarrain.com \
--cc=jengelh@computergmbh.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®