Bug#510261: mdadm: After install if sync is not done when rebooting, it starts over

[John McMonagle]

Neil Brown wrote:
> On Wednesday February 4, madduck at debian.org wrote:
>   
>> tags 510261 confirmed upstream
>> forwarded 510261 neilb at suse.de
>> thanks
>>
>> also sprach John McMonagle <johnm at advocap.org> [2008.12.30.2214 +0100]:
>>     
>>> In both cases I rebooted before the sync was done.
>>> In both cases arrays re-synced from the beginning.
>>> After it finished syncing a reboot does not cause a re-sync.
>>>       
>> This is something Neil would need to fix in the kernel. I think
>> I remember there being some talk about that, but I may misremember.
>> There is nothing mdadm can do against that, I think.
>>     
>
> No, this has nothing to do with mdadm.
>
> But it should not behave like this, and in my experience it doesn't.
>
> There was a bug related to this that was fixed in 2.6.25, but I'm
> fairly sure lenny has a more recent kernel than that (??).
>
> How exactly did you reboot?  Just "shutdown now" or "/sbin/reboot" or
> "turn power off" or ...
>
> Exactly what kernel is used during the install?
>
> NeilBrown
>   
Neil

Wish I could be sure but pretty sure  I used reboot command.
In the most recent case have 2 1-tb drives and recall it resyncing at 
least twice.

Looking at the installer logs. Did install  2008-12-15.
Installer syslog gives says 2.6.26-1-486  Changed to  2.6.26-1-686.

John

-- 
John McMonagle
IT Manager
Advocap Inc.