re: Unexpected RAIDframe behavior

[John Klos <john%ziaspace.com@localhost>]

> what does raidctl -s and -m (separate commands) say?

raidctl -s raid0
Components:
           /dev/wd0a: optimal
           /dev/wd1a: optimal
No spares.
Component label for /dev/wd0a:
   Row: 0, Column: 0, Num Rows: 1, Num Columns: 2
   Version: 2, Serial Number: 2013090100, Mod Counter: 75
   Clean: No, Status: 0
   sectPerSU: 128, SUsPerPU: 1, SUsPerRU: 1
   Queue size: 100, blocksize: 512, numBlocks: 3873470720
   RAID Level: 1
   Autoconfig: Yes
   Root partition: Yes
   Last configured as: raid0
Component label for /dev/wd1a:
   Row: 0, Column: 1, Num Rows: 1, Num Columns: 2
   Version: 2, Serial Number: 2013090100, Mod Counter: 75
   Clean: No, Status: 0
   sectPerSU: 128, SUsPerPU: 1, SUsPerRU: 1
   Queue size: 100, blocksize: 512, numBlocks: 3873470720
   RAID Level: 1
   Autoconfig: Yes
   Root partition: Yes
   Last configured as: raid0
Parity status: DIRTY
Reconstruction is 100% complete.
Parity Re-write is 79% complete.
Copyback is 100% complete.



raidctl -m raid0
raid0: parity map enabled with 4096 regions of 462MB
raid0: regions marked clean after 8 intervals of 40.000s
raid0: write/sync/clean counters 43509/2112/1712
raid0: 871 dirty regions
raid0: parity map will remain enabled on next configure