From owner-freebsd-stable@FreeBSD.ORG Mon Jun 12 11:59:45 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2ECD116A418 for ; Mon, 12 Jun 2006 11:59:45 +0000 (UTC) (envelope-from greg.lane@internode.on.net) Received: from smtp1.adl2.internode.on.net (smtp1.adl2.internode.on.net [203.16.214.181]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6265E43D46 for ; Mon, 12 Jun 2006 11:59:44 +0000 (GMT) (envelope-from greg.lane@internode.on.net) Received: from router.lane.family (ozlane.net [150.101.115.95]) by smtp1.adl2.internode.on.net (8.13.6/8.13.5) with ESMTP id k5CBxYns000913; Mon, 12 Jun 2006 21:29:35 +0930 (CST) (envelope-from greg.lane@internode.on.net) Received: from router.lane.family (localhost.lane.family [127.0.0.1]) by router.lane.family (8.13.4/8.13.4) with ESMTP id k5CBxYAr039742; Mon, 12 Jun 2006 21:59:34 +1000 (EST) (envelope-from gjl103@router.lane.family) Received: (from gjl103@localhost) by router.lane.family (8.13.4/8.13.4/Submit) id k5CBxYYt039741; Mon, 12 Jun 2006 21:59:34 +1000 (EST) (envelope-from gjl103) Date: Mon, 12 Jun 2006 21:59:33 +1000 From: Greg Lane To: "Michael P. Soulier" Message-ID: <20060612115933.GB10678@router.lane.family> References: <20060612055143.GA10925@router.lane.family> <448D30EC.1070400@quip.cz> <20060612104756.GL17400@tigger.digitaltorque.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060612104756.GL17400@tigger.digitaltorque.ca> User-Agent: Mutt/1.4.2.1i Cc: stable@freebsd.org Subject: Re: kernel panic(?) trying to copy data off failed drive with dd X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: greg.lane@internode.on.net List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Jun 2006 11:59:45 -0000 On Mon, Jun 12, 2006 at 06:47:56AM -0400, "Michael P. Soulier" wrote: > On 12/06/06 Miroslav Lachman said: > > Regardless, file a bug report. The box should never hang, or reboot. Is this the case? I had another box (a piece of crap I played around on) that had a failing disk, and this would bring the machine down. So I didn't think this was necessarily unusual. However, on the previous occasion the disk was the root file system with swap on it, whereas in this case, the disk is only a data disk, not any part of the OS. Are you saying that the box should never hang or reboot, but should recover from the error, and whatever command was running should fail and return an error message? If that is the case, is there possibly some sysctl or boot setting that I might have set that would cause it to fail catastrophically rather than properly. Maybe disabling DMA would help? Something? Anything? If people think this is abnormal enough to warrant a bug report, I am happy to file one. I want to be sure this is unexpected behaviour though. Some terse info here, in case it helps: 5.5-PRERELEASE from Wed May 10 Tyan Thunder K8S 2880 UGNR (onboard vga, mpt scsi, dual bge ethernet) 4 x 1GB DDR400 2 x Opteron 248 1 x 73 GB SCSI (Maxtor) (/ /usr etc, plus 1 x 6 GB swap on here) 1 x 147 GB SCSI (Maxtor) (/home, plus 1 x 6 GB swap on here) 2 x SATA 250GB (WD) (data disks, it is one of these that has failed) 1 x ATA 250GB (WD) (scratch disk) Adaptec 2940 with a DLT and EXABYTE drive I can send a dmesg directly if anyone has any ideas. Greg