Re: Reliability of bitmapped resync

[Bill Davidsen <davidsen@tmr.com>]

Neil Brown wrote:
> On Tuesday February 24, piergiorgio.sartor@nexgo.de wrote:
>   
>> Hi,
>>
>>     
>>> I'll wait for these details before I start hunting further.
>>>       
>> OK, here we are.
>> Some forewords, the last disk to fail at boot was
>> /dev/sda, this data was collected after a "clean"
>> add of the /dev/sda3 to the RAID.
>> This means the superblock was zeroed and the device
>> added, so it should be clean.
>>
>>     
> ....
>
> Thanks a lot for that.
>
>   
>> Now, one thing I do not understand, but maybe it is
>> anyway OK, and it is this last line:
>>
>>           Bitmap : 945199 bits (chunks), 524289 dirty (55.5%)
>>
>> Because the array status was fully recovered (in sync)
>> and /dev/sdb3 showed:
>>
>>           Bitmap : 945199 bits (chunks), 1 dirty (0.0%)
>>
>> Confirmed somehow by /proc/mdstat
>>
>> How it could be 55.5% dirty? Is this expected?
>>     
>
> This is a bug.  Is fixed by a patch that I have queued for 2.6.30.  As
> it doesn't cause a crash or data corruption, it doesn't get to jump
> the queue.  It is very small though:
>   

Belatedly I ask if this went to -stable for 2.6.29.

-- 
Bill Davidsen <davidsen@tmr.com>
  "Woe unto the statesman who makes war without a reason that will still
  be valid when the war is over..." Otto von Bismark