Re: Help - raid not assembling right on boot (was: Resizing a RAID1)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, Jan 27, 2011 at 2:47 PM, NeilBrown <neilb@xxxxxxx> wrote:
>>
>>  ÂDevice Boot   ÂStart     End   ÂBlocks  Id ÂSystem
>> /dev/sdb1 Â Â Â Â Â Â2048 Â Â20973567 Â Â10485760 Â fd ÂLinux raid autodetect
>> /dev/sdb2 Â Â Â Â20973568 Â3907029167 Â1943027800 Â fd ÂLinux raid autodetect
>
> These start numbers are multiples of 64K.
>
> With 0.90 metadata, md thinks that the metadata for a partition that starts
> at a multiple of 64K and ends a the end of the device looks just like metadata
> for the whole devices.
>
> If you use 1.0 (or 1;1 or 1.2) metadata this problem will disappear.

Many thanks for the tip.

============
              1, 1.0, 1.1, 1.2
                     Use the new version-1 format superblock.   This
has  few  restricâ
                     tions.   The different sub-versions store the
superblock at differâ
                     ent locations on the device, either at the end
(for  1.0),  at  the
                     start (for 1.1) or 4K from the start (for 1.2).
============

I went with 1.1 and that seems to work w/out this problem.

thanks,
hank

-- 
'03 BMW F650CS - hers
'98 Dakar K12RS - "BABY K" grew up.
'93 R100R w/ Velorex 700 (MBD starts...)
'95 Miata - "OUR LC"
polish visor: apply squashed bugs, rinse, repeat
Beautiful Sunny Winfield, Illinois
--
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


[Index of Archives]     [Linux RAID Wiki]     [ATA RAID]     [Linux SCSI Target Infrastructure]     [Linux Block]     [Linux IDE]     [Linux SCSI]     [Linux Hams]     [Device Mapper]     [Device Mapper Cryptographics]     [Kernel]     [Linux Admin]     [Linux Net]     [GFS]     [RPM]     [git]     [Yosemite Forum]


  Powered by Linux