From owner-freebsd-bugs@FreeBSD.ORG Thu Feb 16 12:40:21 2006 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 DD4DB16A424 for ; Thu, 16 Feb 2006 12:40:21 +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 9776843D5A for ; Thu, 16 Feb 2006 12:40:17 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id k1GCeEWj037060 for ; Thu, 16 Feb 2006 12:40:14 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k1GCeE5C037059; Thu, 16 Feb 2006 12:40:14 GMT (envelope-from gnats) Date: Thu, 16 Feb 2006 12:40:14 GMT Message-Id: <200602161240.k1GCeE5C037059@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org From: phillip@it.jcu.edu.au Cc: Subject: Re: kern/92518: Intense disk activity (large FS newfs and/or many small files copy): DMA completion error with RocketRAID-1820A and FastTRAK-S150 X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: phillip@it.jcu.edu.au List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Feb 2006 12:40:22 -0000 The following reply was made to PR kern/92518; it has been noted by GNATS. From: phillip@it.jcu.edu.au To: bug-followup@freebsd.org Cc: phillip@it.jcu.edu.au Subject: Re: kern/92518: Intense disk activity (large FS newfs and/or many small files copy): DMA completion error with RocketRAID-1820A and FastTRAK-S150 Date: Thu, 16 Feb 2006 22:37:43 +1000 The following work-around for this bug has proved successful: 1) use the RocketRAID for a RAID-1 arrays constructed on pairs of disks. Assuming same sized disks, you'll end up with same sized RAID-1 arrays. 2) instead of using the RocketRAID drivers for striping to produce a RAID-10 array, use a GEOM stripe across the RAID-1 arrays. This allows newfs of 240GB file systems with no problems, and test copies of large numbers of small files (such as are in /usr/ports and /usr/src) also works fine. In addition, the RocketRAID driver can still manage on-line spare disks in the underlying RAID-1 arrays. The speculation that led to this work-around was that perhaps the EDMA time outs are being caused by events being confused between the RocketRAID software drivers associated with RAID-1 and RAID-0. Having RocketRAID handle RAID-1 and GEOM handle higher levels gets around this. However, I have not tested this speculation. The RocketRAID RAID-1 + GEOM stripe arrays have been in normal use for about almost week. It looks good. Note system update: the system has gone from 6.0-STABLE to 6.1-PRERELEASE during which the RocketRAID driver has not changed.