From owner-freebsd-fs@FreeBSD.ORG Tue Jul 20 16:49:01 2010 Return-Path: Delivered-To: fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 764B41065677 for ; Tue, 20 Jul 2010 16:49:01 +0000 (UTC) (envelope-from mi+thun@aldan.algebra.com) Received: from mail2.timeinc.net (mail2.timeinc.net [64.236.74.30]) by mx1.freebsd.org (Postfix) with ESMTP id 2270D8FC27 for ; Tue, 20 Jul 2010 16:49:00 +0000 (UTC) Received: from mail.timeinc.net (mail.timeinc.net [64.12.55.166]) by mail2.timeinc.net (8.13.8/8.13.8) with ESMTP id o6KGmxW4021589 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 20 Jul 2010 12:48:59 -0400 Received: from ws-mteterin.dev.pathfinder.com (ws-mteterin.dev.pathfinder.com [209.251.223.173]) by mail.timeinc.net (8.13.8/8.13.8) with SMTP id o6KGmwQ3030470; Tue, 20 Jul 2010 12:48:59 -0400 Message-ID: <4C45D37A.5020304@aldan.algebra.com> Date: Tue, 20 Jul 2010 12:48:58 -0400 From: "Mikhail T." Organization: Virtual Estates, Inc. User-Agent: Mozilla/5.0 (X11; U; Linux i686; uk; rv:1.9.1.10) Gecko/20100512 Lightning/1.0b1 Thunderbird/3.0.5 MIME-Version: 1.0 To: Kirk McKusick References: <201007201544.o6KFipaV084986@chez.mckusick.com> In-Reply-To: <201007201544.o6KFipaV084986@chez.mckusick.com> Content-Type: text/plain; charset=KOI8-R; format=flowed Content-Transfer-Encoding: 8bit X-Mailman-Approved-At: Tue, 20 Jul 2010 17:45:10 +0000 Cc: fs@freebsd.org Subject: background fsck considered harmful? (Re: panic: handle_written_inodeblock: bad size) X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Jul 2010 16:49:01 -0000 20.07.2010 11:44, Kirk McKusick ΞΑΠΙΣΑΧ(ΜΑ): > Adding it to all the panic's will be a lot of work, > but I agree would be useful. I will look into doing so when I > get a chance. > > Kirk McKusick > How about disabling background fsck in a default install? It seems to be the consensus here, that my troubles were due to fsck not fixing the file-system properly reboot after reboot... Yours, -mi