From owner-freebsd-questions@FreeBSD.ORG Tue Dec 8 10:45:06 2009 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DBC161065676 for ; Tue, 8 Dec 2009 10:45:06 +0000 (UTC) (envelope-from cronfy@sprinthost.ru) Received: from odin.from.sh (odin.from.sh [80.93.50.112]) by mx1.freebsd.org (Postfix) with ESMTP id 974A38FC24 for ; Tue, 8 Dec 2009 10:45:06 +0000 (UTC) Received: from odin.from.sh ([80.93.50.112]) by odin.from.sh with esmtps (TLSv1:AES256-SHA:256) (Exim 4.69 (FreeBSD)) (envelope-from ) id 1NHxVb-00052F-TZ for freebsd-questions@freebsd.org; Tue, 08 Dec 2009 13:41:31 +0300 Received: from [194.8.176.106] (helo=[192.168.0.3]) by odin.from.sh with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69 (FreeBSD)) (envelope-from ) id 1NHxVR-00051U-M8 for freebsd-questions@freebsd.org; Tue, 08 Dec 2009 13:41:22 +0300 Message-ID: <4B1E2DBF.90901@sprinthost.ru> Date: Tue, 08 Dec 2009 13:43:11 +0300 From: cronfy User-Agent: Thunderbird 2.0.0.23 (Windows/20090812) MIME-Version: 1.0 To: freebsd-questions@freebsd.org References: <4B1DF953.4050504@sprinthost.ru> <4B1E2954.8020407@cyberleo.net> In-Reply-To: <4B1E2954.8020407@cyberleo.net> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: FreeBSD is too filesystem errors sensitive X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Dec 2009 10:45:06 -0000 >>> .. but the hell why is it required to panic and kill everything >>> that would be working happily even if something very disasterous >>> happen to /backup partition, in example? >>> >> All those errors indicate file system corruption. To protect other data >> from getting corrupted (e.g. by invalid pointers or calculations), the >> kernel panics. >> > ...and (hopefully) reboots, determines that there were filesystem > errors, and attempts to correct them with fsck(8) Why isn't it possible to do the same without a reboot?