Unforgiving Software Raid (2.4.20)

[David Bandel]

On 11/1/05, Matthew Carpenter <matt at eisgr.com> wrote:
> Does this strike anyone else as rather nasty?
>
>         md: kicking non-fresh hda3 from array!
>
>
> Here's the context:
>         md: created md3
>         md: bind<hda3,1>
>         md: bind<hdc3,2>
>         md: running: <hdc3><hda3>
>         md: hdc3's event counter: 0000002c
>         md: hda3's event counter: 0000002a
>         md: superblock update time inconsistency -- using the most recent one
>         md: freshest: hdc3
>         md: kicking non-fresh hda3 from array!
>         md: unbind<hda3,1>
>         md: export_rdev(hda3)
>
> In my old Novell days, this behavior would send NetWare into rebuild mode.
> Instead of just booting the offender, it recovered.  Perhaps I can see a
> reason for having this behavior, but is there any way to tell the Linux
> kernel to bite the bullet and resync the disks?
>

I suggest you:

fail the disk and remove it from the raid

add the disk back to the raid (whence it should rebuild)

Not seen this myself.  Very stange.

Ciao,

David A. Bandel
--
Focus on the dream, not the competition.
            - Nemesis Air Racing Team motto