From owner-freebsd-bugs Thu Oct 19 21:20: 6 2000 Delivered-To: freebsd-bugs@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 27DEF37B661 for ; Thu, 19 Oct 2000 21:20:03 -0700 (PDT) Received: (from gnats@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id VAA66145; Thu, 19 Oct 2000 21:20:03 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Date: Thu, 19 Oct 2000 21:20:03 -0700 (PDT) Message-Id: <200010200420.VAA66145@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Andy Newman Subject: Re: kern/22103: 4.1-R with Adaptec and Vinum crashes on periodic daily Reply-To: Andy Newman Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR kern/22103; it has been noted by GNATS. From: Andy Newman To: freebsd-gnats-submit@FreeBSD.org, roman@xpert.com Cc: Subject: Re: kern/22103: 4.1-R with Adaptec and Vinum crashes on periodic daily Date: Fri, 20 Oct 2000 15:11:04 +1100 You don't say how vinum if configured. RAID 5 by any chance? It looks exactly like something I ran into a while back with a 29160 based system. In my casual glancing at the various "control blocks" being used it looked like outstanding requests complete after the parent data structure is freed (at least the pointers are NULL). This was all a little while ago and the details are a little sketchy. Only RAID 5 exhibited the problem. I'm running the array as RAID 0 with no problems. -- Andy Newman, Principal Software Engineer, Silverbrook Research To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message