On Wed, 21 Mar 2012 17:21:55 +0400 CoolCold <coolthecold@xxxxxxxxx> wrote: > Btw, was interested in, where bitmap will be placed when adding it on > live array? I.e. as it requires some diskspace, we should provide some > free space, but where it can be taken from if array is already created > and used by, say filesystem? For 0.90 metadata there is 60K of unused space after the superblock. The bitmap is stored there. For 1.x, the metadata stores a data_offset and data_size. All array data is in that range. Anything out side there is available for mdadm to use. When mdadm creates an array it reserves enough space for bitmap and possible other uses. NeilBrown > > On Tue, Mar 20, 2012 at 1:40 AM, Larkin Lowrey > <llowrey@xxxxxxxxxxxxxxxxx> wrote: > > On 3/19/2012 4:32 PM, NeilBrown wrote: > >> On Mon, 19 Mar 2012 11:44:45 -0500 Larkin Lowrey > > <llowrey@xxxxxxxxxxxxxxxxx> > >> wrote: > >> > >>> The following command oopsed. > >>> > >>> mdadm -G --bitmap=internal /dev/md0 > >>> > >>> The array is a two disk raid1 and hosts the root filesystem. > >>> > >>> Is it not possible/allowed to add a bitmap to an active/mounted array? > >> > >> It is. But it is busted. > >> > >> Either use an older mdadm (3.2.2 or earlier), or apply this patch > >> > >> http://neil.brown.name/git?p=md;a=commitdiff;h=4474ca42e2577563a919fd3ed782e2ec55bf11a2 > >> > >> which has been sent to Linus already and should appear in -stable > > kernels in > >> a couple of weeks. > >> > >> NeilBrown > > > > Thank you for the explanation. > > > > --Larkin > > > > -- > > 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 > > >
Attachment:
signature.asc
Description: PGP signature
