From owner-freebsd-current Thu Jun 1 21:22: 2 2000 Delivered-To: freebsd-current@freebsd.org Received: from wantadilla.lemis.com (wantadilla.lemis.com [192.109.197.80]) by hub.freebsd.org (Postfix) with ESMTP id 0315737BE0A; Thu, 1 Jun 2000 21:21:48 -0700 (PDT) (envelope-from grog@wantadilla.lemis.com) Received: (from grog@localhost) by wantadilla.lemis.com (8.9.3/8.9.3) id NAA25621; Fri, 2 Jun 2000 13:51:42 +0930 (CST) (envelope-from grog) Date: Fri, 2 Jun 2000 13:51:42 +0930 From: Greg Lehey To: FreeBSD current users , FreeBSD Stable Users Subject: HEADS UP: Data corruption bug in Vinum found and fixed Message-ID: <20000602135142.K22978@wantadilla.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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 grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message