Re: recovery starts from 0 after reboot - normal?

[Tomasz Chmielewski <mangoo@wpkg.org>]

Justin Piszcz schrieb:

>> According to the fine manual, BITMAP CHANGES belong to the grow mode.
>> So, let's try to do what the manual says - try to add a bitmap to the 
>> active array:
>>
>>
>> # mdadm --grow /dev/md0 --bitmap=internal
>> mdadm: failed to set internal bitmap.
>>
>> # dmesg
>> md: couldn't update array info. -16
>>
>>
>> So, either I don't understand the manual, or there are more caveats in 
>> it.

(...)

> Check: http://lkml.org/lkml/2007/6/17/235

It's an external bitmap; I'd prefer an internal one, as my root 
filesystem is on a flash-IDE disk.

However, let's try the external bitmap:

# mdadm --grow /dev/md0 --bitmap=/bitmapfile
mdadm: Cannot set bitmap file for /dev/md0: Device or resource busy


So, it also fails. Perhaps because the array still rebuilds?

A 95644 byte /bitmapfile was created.


I'll try again when the array is done with rebuilding. According to 
/proc/mdstat, it would be 6 more hours.


-- 
Tomasz Chmielewski
http://wpkg.org