Re: raidframe fun

[Greg Oster <oster%cs.usask.ca@localhost>]

On Fri, 16 Aug 2013 22:15:00 +0100
Patrick Welche <prlw1%cam.ac.uk@localhost> wrote:

> I thought this one was amusing:
> 
> quantz# raidctl -s raid6
> Components:
>           component0: failed
>            /dev/wd3a: optimal
> No spares.
> component0 status is: failed.  Skipping label.
> Component label for /dev/wd3a:
>    Row: 0, Column: 1, Num Rows: 1, Num Columns: 2
>    Version: 2, Serial Number: 2009120800, Mod Counter: 359
>    Clean: No, Status: 0
>    sectPerSU: 128, SUsPerPU: 1, SUsPerRU: 1
>    Queue size: 100, blocksize: 512, numBlocks: 20971264
>    RAID Level: 1
>    Autoconfig: Yes
>    Root partition: Yes
>    Last configured as: raid6
                         ^^^^^
> Parity status: clean
> Reconstruction is 100% complete.
> Parity Re-write is 100% complete.
> Copyback is 100% complete.
> quantz# raidctl -s raid4
> Components:
>            /dev/wd2a: optimal
>           component1: failed
> No spares.
> Component label for /dev/wd2a:
>    Row: 0, Column: 0, Num Rows: 1, Num Columns: 2
>    Version: 2, Serial Number: 2009120800, Mod Counter: 363
>    Clean: No, Status: 0
>    sectPerSU: 128, SUsPerPU: 1, SUsPerRU: 1
>    Queue size: 100, blocksize: 512, numBlocks: 20971264
>    RAID Level: 1
>    Autoconfig: Yes
>    Root partition: Yes
>    Last configured as: raid4
                         ^^^^^
They've gotten split up before.... did you perchance only bring up the
one disk one time, and move it to a different raid number?  (e.g. from
raid1 to raid4 or whatever?)

> component1 status is: failed.  Skipping label.
> Parity status: DIRTY
> Reconstruction is 100% complete.
> Parity Re-write is 100% complete.
> Copyback is 100% complete.
> 
> They didn't quite find each other again...

Right.. so the question is why?  This is not supposed to happen (and
the only way I've ever seen it happen before is if a User gets playing
tricks with the raid devices and attempts to re-combine components
after they've been configured to different RAID sets...)

Later...

Greg Oster