From owner-freebsd-stable@FreeBSD.ORG Sat Dec 8 07:43:33 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id AEE82ABA for ; Sat, 8 Dec 2012 07:43:33 +0000 (UTC) (envelope-from tomek.cedro@gmail.com) Received: from mail-lb0-f182.google.com (mail-lb0-f182.google.com [209.85.217.182]) by mx1.freebsd.org (Postfix) with ESMTP id 2462C8FC16 for ; Sat, 8 Dec 2012 07:43:32 +0000 (UTC) Received: by mail-lb0-f182.google.com with SMTP id go10so1206049lbb.13 for ; Fri, 07 Dec 2012 23:43:31 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; bh=yU4BsP1ow8hXE72PxH95HW15lVJv5+XLLtuTDe+RnIU=; b=bH9D5d24SSBIyN6T+KPH5zli0MT2n5h6AUx2HeY5pMPwTkpyt/YO/hWqPY1yaDOK2s p4XiZX3GjsU4W9xigcPxIaEx+ZEvmrc0ld7Fz7C2fAirC7NHpZbwqqTiC4CRvk/OPoCO X10Dr6RED97kB13GvVFtFbJh35f7CTOCsgRv8p3Vib/hGBhRTzA9hy4rF4rxM+PxUTef 942nWydYxJnUs7ATLGXEutPCUyuNC/jHJJwuvaO17dS9txlVDYpx5K1cJ6u7oDJGLUsX ONQtiA07vKy/7p3aCgu76an6j2Pwod1ASIPwbwGH1BtseTFrfZvj/B7sWD7uIW5AiM7y OD4A== MIME-Version: 1.0 Received: by 10.112.84.102 with SMTP id x6mr3598534lby.35.1354952611621; Fri, 07 Dec 2012 23:43:31 -0800 (PST) Sender: tomek.cedro@gmail.com Received: by 10.114.12.226 with HTTP; Fri, 7 Dec 2012 23:43:31 -0800 (PST) Received: by 10.114.12.226 with HTTP; Fri, 7 Dec 2012 23:43:31 -0800 (PST) In-Reply-To: References: Date: Sat, 8 Dec 2012 08:43:31 +0100 X-Google-Sender-Auth: MhyPD_k2JJ3VkrilkvQXBr_7uHI Message-ID: Subject: Re: 9.1-RC3 reproducible kernel panic in ffs_valloc? From: CeDeROM To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 08 Dec 2012 07:43:33 -0000 This problem was caused by corrupted UFS2-SU+J (9.x default) filesystem marked as clean where journal showed no issues, running fsck -t ufs -fy solved the issue! http://i47.tinypic.com/35m1qxk.jpg I guess filesystem related kernel panic should enforce full filesystem chceck (some filesystem flag or journal date modification to enforce full check). Maybe it is possible to stop the OS in that case, perform some sort of fsck running from memory, and then continue the OS with no crash? :-) Best regards :-) Tomek -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info