From nobody@FreeBSD.org  Sat Dec  8 15:12:36 2012
Return-Path: <nobody@FreeBSD.org>
Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52])
	by hub.freebsd.org (Postfix) with ESMTP id B17DC9C5
	for <freebsd-gnats-submit@FreeBSD.org>; Sat,  8 Dec 2012 15:12:36 +0000 (UTC)
	(envelope-from nobody@FreeBSD.org)
Received: from red.freebsd.org (red.freebsd.org [IPv6:2001:4f8:fff6::22])
	by mx1.freebsd.org (Postfix) with ESMTP id 977788FC0C
	for <freebsd-gnats-submit@FreeBSD.org>; Sat,  8 Dec 2012 15:12:36 +0000 (UTC)
Received: from red.freebsd.org (localhost [127.0.0.1])
	by red.freebsd.org (8.14.5/8.14.5) with ESMTP id qB8FCZnJ036869
	for <freebsd-gnats-submit@FreeBSD.org>; Sat, 8 Dec 2012 15:12:35 GMT
	(envelope-from nobody@red.freebsd.org)
Received: (from nobody@localhost)
	by red.freebsd.org (8.14.5/8.14.5/Submit) id qB8FCZJ3036868;
	Sat, 8 Dec 2012 15:12:35 GMT
	(envelope-from nobody)
Message-Id: <201212081512.qB8FCZJ3036868@red.freebsd.org>
Date: Sat, 8 Dec 2012 15:12:35 GMT
From: Tomasz CEDRO <cederom@tlen.pl>
To: freebsd-gnats-submit@FreeBSD.org
Subject: UFS2-SU+J journal and filesystem corruption
X-Send-Pr-Version: www-3.1
X-GNATS-Notify:

>Number:         174279
>Category:       kern
>Synopsis:       [ufs] UFS2-SU+J journal and filesystem corruption
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-fs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sat Dec 08 15:20:00 UTC 2012
>Closed-Date:    
>Last-Modified:  Sat Dec 08 15:27:51 UTC 2012
>Originator:     Tomasz CEDRO
>Release:        FreeBSD 9.1-RC3
>Organization:
CeDeROM
>Environment:
FreeBSD hexagon 9.1-RC3 FreeBSD 9.1-RC3 #0 r242324: Tue Oct 30 00:58:57 UTC 2012     root@farrell.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC  amd64

>Description:
The / (root) filesystem was currupted somehow by a crash/power failure (not hard drive or badblock malfunction). Although su-journal check did not show anything wrong underlying filesystem was corrupted and that lead to further kernel panic on each boot.

http://i45.tinypic.com/23qtcx.jpg

http://i47.tinypic.com/35m1qxk.jpg
>How-To-Repeat:

>Fix:
I guess filesystem related (or any?) kernel panic should enforce full filesystem chceck (some filesystem flag or journal timestamp modification to enforce full check).

Maybe it is possible to stop the OS in that case (filesystem), perform some sort of fsck running from memory, and then continue one time again the OS with no crash? :-)

>Release-Note:
>Audit-Trail:
Responsible-Changed-From-To: freebsd-bugs->freebsd-fs 
Responsible-Changed-By: eadler 
Responsible-Changed-When: Sat Dec 8 15:27:29 UTC 2012 
Responsible-Changed-Why:  
fix synopsis and assign 

http://www.freebsd.org/cgi/query-pr.cgi?pr=174279 
>Unformatted:
