From owner-freebsd-bugs@FreeBSD.ORG Thu Nov 10 13:10:19 2005 Return-Path: X-Original-To: freebsd-bugs@hub.freebsd.org Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B591916A41F for ; Thu, 10 Nov 2005 13:10:19 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6FD5343D46 for ; Thu, 10 Nov 2005 13:10:19 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id jAADAJlE027004 for ; Thu, 10 Nov 2005 13:10:19 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id jAADAJE5027002; Thu, 10 Nov 2005 13:10:19 GMT (envelope-from gnats) Date: Thu, 10 Nov 2005 13:10:19 GMT Message-Id: <200511101310.jAADAJE5027002@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org From: David Kirchner Cc: Subject: Re: kern/50201: [twe] 3ware RAID 5 resulting in data corruption X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: David Kirchner List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Nov 2005 13:10:19 -0000 The following reply was made to PR kern/50201; it has been noted by GNATS. From: David Kirchner To: bug-followup@FreeBSD.org, bruce@engmail.uwaterloo.ca Cc: Subject: Re: kern/50201: [twe] 3ware RAID 5 resulting in data corruption Date: Wed, 9 Nov 2005 12:16:16 -0800 I'm wondering if this bug is still in the system. I've personally been using 3ware cards on 4.5 machines and beyond without data corruption: RAID5 w/ WC enabled and other RAID configurations (1, 10). The driver has also been updated relatively recently. Bruce, I'm not suggesting tha this bug is definitely fixed, but I'm curious, are you still having trouble with RAID5? If not, can we close this bug?