Setting write-intent bitmap during array resync/create?

Setting write-intent bitmap during array resync/create?

[Eli Stair]

I gather this isn't currently possible, but I wonder if it's feasible to 
make it so?  This works fine once the array is marked 'clean', and I 
imagine it's simpler to just disallow the bitmap creation until it's in 
that state.  Would it be possible to allow creation of the bitmap by 
queueing the action until the array is done rebuilding?

The reason for this concern is I've got a plethora of systems that are 
set for auto-deployment; that is they can be booted into a mode where 
they will have no existing array and will create it from scratch.  I 
will be using the write-intent bitmap, but in the present state I have 
to set a job to monitor the array state and manually issue the create 
command when it is finished building.

It seems a good candidate for being able to specify this option at array 
creation time along with all other options.

Just a suggestion/feature request.

Cheers,

/eli



// WI Bitmap creation attempt:

[root@gtmp08 /]# mdadm /dev/md0 -Gb internal

mdadm: failed to set internal bitmap.
md: couldn't update array info. -16



// MD state:

Personalities : [raid10]
md0 : active raid10 dm-9[13] dm-8[12] dm-7[11] dm-6[10] dm-5[9] dm-4[8] 
dm-3[7] dm-2[6] dm-13[5] dm-11[4] dm-12[3] dm-10[2] dm-1[1] dm-0[0]
       1003620352 blocks super 1.2 512K chunks 2 offset-copies [14/14] 
[UUUUUUUUUUUUUU]
       [==>..................]  resync = 12.2% (123160576/1003620352) 
finish=225.5min speed=65050K/sec

unused devices: <none>

Re: Setting write-intent bitmap during array resync/create?

[dean gaudet]

On Tue, 10 Oct 2006, Eli Stair wrote:

> I gather this isn't currently possible, but I wonder if it's feasible to make
> it so?  This works fine once the array is marked 'clean', and I imagine it's
> simpler to just disallow the bitmap creation until it's in that state.  Would
> it be possible to allow creation of the bitmap by queueing the action until
> the array is done rebuilding?

why don't you add "-b internal" to the mdadm --create command line?  

-dean

Re: Setting write-intent bitmap during array resync/create?

[Eli Stair]

[-- Attachment #1: Type: text/plain, Size: 860 bytes --]




> On Tue, 10 Oct 2006, Eli Stair wrote:
> 
>  > I gather this isn't currently possible, but I wonder if it's feasible 
> to make
>  > it so?  This works fine once the array is marked 'clean', and I 
> imagine it's
>  > simpler to just disallow the bitmap creation until it's in that 
> state.  Would
>  > it be possible to allow creation of the bitmap by queueing the action 
> until
>  > the array is done rebuilding?

dean gaudet wrote:
> 
> why don't you add "-b internal" to the mdadm --create command line? 
> 
> -dean
> 


Valid question!

One - I apparently made a blunder of the syntax and kept including -G 
out of habit when I formed the create line, and didn't pay attention to 
the error in my logs.  D'oh.

Two - After realizing the mistake, I find there are a few bugs in doing 
this.  Posting a separate new thread for this.


Cheers,

/eli


[-- Attachment #2: mdadm-create-array-with-bitmap-ext3-success.log.gz --]
[-- Type: application/x-gzip, Size: 23083 bytes --]

[-- Attachment #3: mdadm-create-array-with-bitmap-failure.log.gz --]
[-- Type: application/x-gzip, Size: 1998 bytes --]

[-- Attachment #4: mdadm-create-array-with-bitmap_externalfile-fails.log.gz --]
[-- Type: application/x-gzip, Size: 1696 bytes --]

[-- Attachment #5: mdadm-create-array-with-bitmap_externalfile-fails.strace.gz --]
[-- Type: application/x-gzip, Size: 2887 bytes --]

[-- Attachment #6: mdadm-create-array-without-bitmap-success.log.gz --]
[-- Type: application/x-gzip, Size: 1873 bytes --]