Current-Users archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: raidframe oddity



On Mon, Mar 19, 2018 at 12:12:09PM +0000, Patrick Welche wrote:
> On Mon, Mar 19, 2018 at 12:51:20PM +0100, Martin Husemann wrote:
> > On Mon, Mar 19, 2018 at 11:38:20AM +0000, Patrick Welche wrote:
> > > No spares.
> > > Component label for /dev/dk17:
> > >    Row: 1, Column: 3, Num Rows: 0, Num Columns: 0
> > >    Version: 3865, Serial Number: 0, Mod Counter: 0
> > >    Clean: Yes, Status: 1
> > >    sectPerSU: 1, SUsPerPU: 53, SUsPerRU: 100
> > >    Queue size: -387938304, blocksize: -387938208, numBlocks: 3865
> > >    RAID Level: ^@
> > >    Autoconfig: Yes
> > >    Root partition: No
> > >    Last configured as: raid0
> > > 
> > > 
> > > Interesting queue size... (and raid level)
> > 
> > Many raidframe ioctls got versioned, how old is your raidctl? (If old, 
> > please keep it so we can fix the emulation ;-})
> 
> # ls -l `which raidctl`
> -r-xr-xr-x  1 root  wheel  36320 Mar 17 08:38 /sbin/raidctl
> 
> By ancient, I meant it wasn't a new raid. That raid 5 was in that box
> for a while, and that box follows -current/amd64. So, it was created
> with an older raidctl. (Not sure I should start worrying that I don't
> see the cgd on it yet or not...)

Seems it is widespread: just updated another box to 8.99.14/amd64, and
see (raid 1):

# raidctl -s raid0 | more
Components:
           /dev/wd0a: optimal
           /dev/wd1d: optimal
No spares.
Component label for /dev/wd0a:
   Row: 1, Column: 2, Num Rows: 0, Num Columns: 0
   Version: 1883053668, Serial Number: 0, Mod Counter: 0
   Clean: Yes, Status: 1
   sectPerSU: 1, SUsPerPU: 49, SUsPerRU: 100
   Queue size: 147911680, blocksize: 147911840, numBlocks: 1883053668
   RAID Level: ^@
   Autoconfig: No
   Root partition: No
   Last configured as: raid0
...


Home | Main Index | Thread Index | Old Index