From owner-freebsd-fs@FreeBSD.ORG Mon Jul 19 16:48:16 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 1FD72106564A for ; Mon, 19 Jul 2010 16:48:16 +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 BF37F8FC08 for ; Mon, 19 Jul 2010 16:48:15 +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 o6JFtxKR030635 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 19 Jul 2010 11:55: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 o6JFtxsT021007; Mon, 19 Jul 2010 11:55:59 -0400 Message-ID: <4C44758F.7080209@aldan.algebra.com> Date: Mon, 19 Jul 2010 11:55:59 -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: Jeremy Chadwick References: <4C43F35D.5020007@aldan.algebra.com> <20100719113147.GA4786@icarus.home.lan> In-Reply-To: <20100719113147.GA4786@icarus.home.lan> X-Mailman-Approved-At: Mon, 19 Jul 2010 21:14:31 +0000 Content-Type: text/plain; charset=KOI8-R; format=flowed Content-Transfer-Encoding: 8bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: stable@freebsd.org, fs@freebsd.org Subject: 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: Mon, 19 Jul 2010 16:48:16 -0000 19.07.2010 07:31, Jeremy Chadwick ΞΑΠΙΣΑΧ(ΜΑ): > If you boot the machine in single-user, and run fsck manually, are there > any errors? > Thanks, Jeremy... I wish, there was a way to learn, /which/ file-system is giving trouble... However, after sending the question out last night, I tried to pkg_delete a package on the machine, and was very lucky to see a file-system error (inode something or other) before the panic struck. That, at least, told me, which file-system was in trouble (/var). I dump-ed it out, re-created, and then restored it... Although dumping went smooth, there were two errors at which restore offered to abort. I told it not to and got (most of the) file-system restored. (The dump is available to anyone wishing to investigate -- contact me privately. I'm not posting it publicly because of the passwd-file backup under /var). So far seems quiet -- no panics for two more hours before I went to bed. > Only thing I can think of off the top of my head: there's a known > situation (also applies to RELENG_7) where a background fsck doesn't > correct all errors after a system crash/unclean shutdown. I mention > this because I see "softdep" in the above stack trace (usually refers to > softupdates). I don't know if this got fixed, but the workaround is to > use background_fsck="no" in rc.conf. Yes, after a crash this means you > have to wait for the entire fsck to run. > When setting up my main machine 4 years ago, I turned off background fsck... But I thought, things have improved sufficiently enough since then :-( Maybe, background fsck should still be disabled by default? And, IMO, at the very least, *any panic related to a file-system must clearly identify the file-system in question*... What do you think? Yours, -mi