From owner-freebsd-stable@FreeBSD.ORG Mon Jun 12 12:13:16 2006 Return-Path: X-Original-To: freebsd-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 0BB0716A473 for ; Mon, 12 Jun 2006 12:13:16 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (lurza.secnetix.de [83.120.8.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id DB10443D46 for ; Mon, 12 Jun 2006 12:13:14 +0000 (GMT) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (qnunef@localhost [127.0.0.1]) by lurza.secnetix.de (8.13.4/8.13.4) with ESMTP id k5CCD66u062883; Mon, 12 Jun 2006 14:13:12 +0200 (CEST) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.13.4/8.13.1/Submit) id k5CCD6K8062882; Mon, 12 Jun 2006 14:13:06 +0200 (CEST) (envelope-from olli) Date: Mon, 12 Jun 2006 14:13:06 +0200 (CEST) Message-Id: <200606121213.k5CCD6K8062882@lurza.secnetix.de> From: Oliver Fromme To: freebsd-stable@FreeBSD.ORG, greg.lane@internode.on.net In-Reply-To: <20060612115933.GB10678@router.lane.family> X-Newsgroups: list.freebsd-stable User-Agent: tin/1.8.0-20051224 ("Ronay") (UNIX) (FreeBSD/4.11-STABLE (i386)) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.1.2 (lurza.secnetix.de [127.0.0.1]); Mon, 12 Jun 2006 14:13:12 +0200 (CEST) Cc: 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: freebsd-stable@FreeBSD.ORG, 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 12:13:16 -0000 Greg Lane wrote: > Michael P. Soulier wrote: > > > > 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? It depends. Usually the system should _not_ panic in case of software errors. For example, when running fsck on a broken file system, it should not cause a panic. However, mounting a broken file system might cause a panic or other misbehaviour, which is clearly documented as a bug in the mount(8) manpage: "It is possible for a corrupted file system to cause a crash." However, in the case of hardware failures (including broken disk drives), anything bad can happen, ranging from silent data corruption to panics or cold freezes. Any many cases the operating system simply has no chance to deal with it properly. So, if your panic is caused purely by software error, and it's not already known and documented, filing a PR might be a good idea. But if faulty hardware is involved, sending a PR is probably useless. Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing Dienstleistungen mit Schwerpunkt FreeBSD: http://www.secnetix.de/bsd Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. "A language that doesn't have everything is actually easier to program in than some that do." -- Dennis M. Ritchie