vinum revive does not rebuild parity (was vinum rebuildparity, when?)

[Stijn Hoop]

On Fri, Aug 27, 2004 at 02:24:46PM +0200, Christian Laursen wrote:
> Stijn Hoop <stijn at win.tue.nl> writes:
> > On Wed, Aug 25, 2004 at 12:08:53PM +0200, Christian Laursen wrote:
> > > When reviving a disk the data on that disk is calculated from the data
> > > and the parity on the other disks.
> > 
> > Yes, but the parity should be recalculated at the same time, right?
> 
> Yes.

Witness this (after yet another fake disk crash):

%%%

vinum -> ls -v local.p0.s0
Subdisk local.p0.s0:
                Size:      31457129472 bytes (29999 MB)
                State: reviving
                Plex local.p0 at offset 0 (0  B)
                Reviver PID:    46863
                Revive pointer:                 22 GB (77%)
                Revive blocksize:               64 kB
                Revive interval:                 0 seconds
                Drive ren (/dev/ad6s1e) at offset 135680 (132 kB)
 
vinum -> vinum[46863]: local.p0.s0 is up
 
vinum -> checkparity local.p0.s0
local.p0.s0 is not a plex
vinum -> checkparity local.p0
Parity incorrect at offset 0x2020
vinum -> rebuildparity -V local.p0
Parity incorrect at offset 0x2020
Rebuilding at 2703 kB (0%)    Parity incorrect at offset 0x2a6664
Rebuilding at 139 MB (0%)

%%%

which indicates that the parity surely is not correctly recalculated during
the revive.

Greg, can you tell me if this is correct behaviour?

--Stijn

-- 
Q: Why is Batman better than Bill Gates?
A: Batman was able to beat the Penguin.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-questions/attachments/20040829/ab7b5d80/attachment.bin