Re: raidframe oddity

[Martin Husemann <martin%duskware.de@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

Luckily, netbsd-8 is fine (output for same raid0):

# raidctl -s raid0
Components:
           /dev/sd0a: optimal
           /dev/sd1a: optimal
No spares.
Component label for /dev/sd0a:
   Row: 0, Column: 0, Num Rows: 1, Num Columns: 2
   Version: 2, Serial Number: 5939533, Mod Counter: 12422
   Clean: No, Status: 0
   sectPerSU: 128, SUsPerPU: 1, SUsPerRU: 1
   Queue size: 100, blocksize: 512, numBlocks: 17773440
   RAID Level: 1
   Autoconfig: Yes
   Root partition: Soft
   Last configured as: raid0
Component label for /dev/sd1a:
   Row: 0, Column: 1, Num Rows: 1, Num Columns: 2
   Version: 2, Serial Number: 5939533, Mod Counter: 12422
   Clean: No, Status: 0
   sectPerSU: 128, SUsPerPU: 1, SUsPerRU: 1
   Queue size: 100, blocksize: 512, numBlocks: 17773440
   RAID Level: 1
   Autoconfig: Yes
   Root partition: Soft
   Last configured as: raid0
Parity status: clean
Reconstruction is 100% complete.
Parity Re-write is 100% complete.
Copyback is 100% complete.


Martin