On Wed Oct 14, 2009 at 03:45:21AM -0400, Antonio Perez wrote: > Robin Hill wrote: > > > On Tue Oct 13, 2009 at 09:13:13AM -0400, Antonio Perez wrote: > > Then, the two consequences of dividing disks in several md are correct: > > 1.- Will improve rebuild time, as each md is smaller. > 2.- Will allow to control if the md is in the outside (faster) disk area. > > Am I understanding you correctly? > Certainly both of these will apply, yes. My understanding is that there'll be little (if any) negative effects from this, but that's based more on what (and where) the tunables are for the IO stack, rather than any knowledge of what's actually going on in it. > There are two areas of interest: > > 1.- The "Boot disk area" including the MBR.: > On the usual (at least for me) partition scheme, the first cylinder*, > Sectors (LBA) 0-62 [CHS 0/0/1 to 0/0/63] of the disk are left empty, except > for sector 0, a.k.a. MBR. That is called the disk boot area. > Grub uses the sector 0 as the MBR and several sectors following it to embed > the booting code: core.img. > > 2.- The "partition boot area": > There is also an empty space at the beginning of each partition of 63 > sectors. The first partition uses (LBA) 63-125 [CHS 0/1/0 to 0/1/63] for the > "partition boot area" therefore restoring alignment on the disk heads. > Next partitions repeat this setup. > This area is used to boot if grub is installed to sda1 instead of sda > > So, I assume that a RAID1 on "sd[a..d]1" will mirror the "Area 2" but will > not touch any of the "Area 1". > > Is this assumption correct? > Yes - anything that falls within the blocks covered by the array will get replicated, so "Area 2" will automatically get taken care of (you'll have to make sure the RAID metadata version is chosen correctly so as not to conflict though - 1.1/1.2 metadata may overlap with the area used by grub here). As for "Area 1" - from what you've written (and reading the grub internals documentation), I can only assume you're referring to the stage1.5 bootloader (unless you're using grub2?). This can live on the file system (I don't see anything obvious in the documentation about how you set where it goes - the documentation seems to suggest that the file system is the default), so so there may well be no need to do anything about this (other than the MBR itself). > >> 2.- Is there a recomended way to trigger the said copy of question 2? > >> Where should a call to copy the MBR should be placed? On update-grub? > > > I always just rerun the grub install for each disk manually (see > > http://lists.us.dell.com/pipermail/linux-poweredge/2003-July/008898.html > > for example). > > That's the usual procedure on a first install, correct. > It's what I do every update - it's a quick enough process, and grub updates aren't very common (all the development's on grub2 now). Cheers, Robin -- ___ ( ' } | Robin Hill <robin@xxxxxxxxxxxxxxx> | / / ) | Little Jim says .... | // !! | "He fallen in de water !!" |
Attachment:
pgpYa7mg8Luws.pgp
Description: PGP signature
