| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <Pine.LNX.4.64.0712010722460.28887@p34.internal.lan> Date: Sat, 1 Dec 2007 07:22:57 -0500 (EST) From: Justin Piszcz <jpiszcz@...idpixels.com> To: Jan Engelhardt <jengelh@...putergmbh.de> cc: linux-kernel@...r.kernel.org, linux-raid@...r.kernel.org, apiszcz@...arrain.com Subject: Re: Kernel 2.6.23.9 + mdadm 2.6.2-2 + Auto rebuild RAID1? 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. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists