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

[Eli Stair <estair@ilm.com>]

[-- 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 --]