>Number:         26741
>Category:       bin
>Synopsis:       "raidctl -S" doesn't always work as expected
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    bin-bug-people
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Mon Aug 23 12:24:00 UTC 2004
>Closed-Date:
>Last-Modified:
>Originator:     
>Release:        NetBSD 2.0_BETA
>Organization:
Matthias Scheler                                  http://scheler.de/~matthias/
>Environment:
System: NetBSD colwyn.zhadum.de 2.0_BETA NetBSD 2.0_BETA (COLWYN) #0: Mon Jul 26 12:22:36 CEST 2004 tron@colwyn.zhadum.de:/src/sys/compile/COLWYN i386
Architecture: i386
Machine: i386
>Description:
My system suffered death by administration a few minutes ago and is now
rewriting the parity on the RAIDframe mirror "raid0". "raidctl -S raid0"
works nicely here:

tron@colwyn:~>raidctl -S raid0
Reconstruction is 100% complete.
Parity Re-write is 0% complete.
Copyback is 100% complete.
Parity Re-write status:
  4% |*                                      | ETA: 01:41:31 /

But although the parity of the other mirror is also dirty ...

tron@colwyn:~>raidctl -s raid1
[...]
Parity status: DIRTY
Reconstruction is 100% complete.
Parity Re-write is 100% complete.
Copyback is 100% complete.

... "raidctl -S raid1" returns immediately as if everything is allright:

tron@colwyn:~>time raidctl -S raid1
Reconstruction is 100% complete.
Parity Re-write is 100% complete.
Copyback is 100% complete.
raidctl -S raid1  0.01s user 0.00s system 354% cpu 0.003 total

It should at least print a warning that the mirror isn't in sync.

>How-To-Repeat:
Hard crash a system with two RAIDframe mirrors. Use "raidctl -S raid1"
while the first mirror is rewriting the parity.

>Fix:
None provided.

>Release-Note:
>Audit-Trail:
>Unformatted: