Re: raidframe oddity

[Patrick Welche <prlw1%cam.ac.uk@localhost>]

On Tue, Mar 20, 2018 at 08:54:13AM +0100, Martin Husemann wrote:
> On Mon, Mar 19, 2018 at 05:36:26PM +0000, Patrick Welche wrote:
> > Seems it is widespread: just updated another box to 8.99.14/amd64, and
> > see (raid 1):
> 
> Indeed, it is broken for me as well:
> 
> # raidctl -s raid0
> Components:
>            /dev/sd0a: optimal
>            /dev/sd1a: optimal
> No spares.
> Component label for :
>    Row: 0, Column: 0, Num Rows: 0, Num Columns: 0
>    Version: 0, Serial Number: 0, Mod Counter: 0
>    Clean: No, Status: 0
>    sectPerSU: 0, SUsPerPU: 0, SUsPerRU: 0
>    Queue size: 0, blocksize: 0, numBlocks: 0
>    RAID Level: 
>    Autoconfig: No
>    Root partition: No
>    Last configured as: raid0
> Parity status: clean
> Reconstruction is 100% complete.
> Parity Re-write is 100% complete.
> Copyback is 100% complete.
> 
> 
> Can you please file a PR?

Yes - and the cgd bit was a confusion over dk numbers in /etc/cgd - much
happier now, as this is just cosmetic :-)

Cheers,

Patrick