From owner-freebsd-scsi@FreeBSD.ORG Thu Mar 10 16:04:32 2005 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C9D7916A4CE; Thu, 10 Mar 2005 16:04:32 +0000 (GMT) Received: from nargothrond.kdm.org (nargothrond.kdm.org [70.56.43.81]) by mx1.FreeBSD.org (Postfix) with ESMTP id 239CD43D5A; Thu, 10 Mar 2005 16:04:32 +0000 (GMT) (envelope-from ken@nargothrond.kdm.org) Received: from nargothrond.kdm.org (localhost [127.0.0.1]) by nargothrond.kdm.org (8.12.11/8.12.11) with ESMTP id j2AG4Twi030489; Thu, 10 Mar 2005 09:04:29 -0700 (MST) (envelope-from ken@nargothrond.kdm.org) Received: (from ken@localhost) by nargothrond.kdm.org (8.12.11/8.12.5/Submit) id j2AG4Tee030488; Thu, 10 Mar 2005 09:04:29 -0700 (MST) (envelope-from ken) Date: Thu, 10 Mar 2005 09:04:29 -0700 From: "Kenneth D. Merry" To: Fritz Heinrichmeyer Message-ID: <20050310160428.GA30406@nargothrond.kdm.org> References: <42303E74.9060301@fernuni-hagen.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <42303E74.9060301@fernuni-hagen.de> User-Agent: Mutt/1.4.2i X-Virus-Scanned: ClamAV 0.83/760/Wed Mar 9 10:12:01 2005 on nargothrond.kdm.org X-Virus-Status: Clean cc: freebsd-scsi cc: freebsd-stable Subject: Re: error messages from easyraid ex array X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Mar 2005 16:04:32 -0000 On Thu, Mar 10, 2005 at 13:32:52 +0100, Fritz Heinrichmeyer wrote: > Hello, > > sometimes i see following messages with FreeBSD-5.3, ahc driver and an > easyraid ex system. We have two identical boxes one connected to another > system has no problem. The problematic error messages occur when > berkeley-db files are massaged by cyrus imap server. > > I cannot believe there is a media error on an raid 5 system that is not > announced at the control panel of the raid box. Well, firmware on the RAID box will do whatever the authors wrote it to do. In theory, you're right. On a non-critical RAID-5 array, they should be able to recover from any single drive read error. If your array is critical, though (i.e. you've lost one disk), you won't be able to recover from a read error. > Driver: > > ahc2: port 0x3800-0x38ff mem > 0xf7ed0000-0xf7ed0fff irq 11 at device 4.0 on pci1 > da1 at ahc2 bus 0 target 5 lun 0 > > Errors: > > (da1:ahc2:0:5:0): READ(10). CDB: 28 0 0 71 6a 4f 0 0 10 0 > (da1:ahc2:0:5:0): CAM Status: SCSI Status Error > (da1:ahc2:0:5:0): SCSI Status: Check Condition > (da1:ahc2:0:5:0): MEDIUM ERROR asc:0,0 > (da1:ahc2:0:5:0): No additional sense information > (da1:ahc2:0:5:0): Retrying Command (per Sense Data) That's a little bit of a strange error, because they only set the sense key but not the asc/ascq. In any case, it looks like we retried it. If the device was still returning errors, you'd eventually see a "Retries Exhausted" message. Ken -- Kenneth Merry ken@FreeBSD.org