I've just discovered (and fixed) a serious data corruption bug in
Vinum. Under certain circumstances, serious data corruption can
result:
1. You are using RAID-4 or RAID-5 plexes.
2. One of these plexes (not the first plex in the system, whether a
RAID-[45] plex or not) develops parity problems.
3. You correct these errors with the 'rebuildparity' command.
Under these circumstances, the corrected blocks will probably be
written to the wrong subdisk. The original parity errors will remain.
The fix is in 4-STABLE and 5-CURRENT (revisions 1.22.2.1 and 1.29,
respectively). I don't think that 3-STABLE currently supports the
rebuildparity command, but I shall check and MFC if necessary.
Greg
--
Finger [EMAIL PROTECTED] for PGP public key
See complete headers for address and phone numbers
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
