>Number: 174279 >Category: misc >Synopsis: UFS2-SU+J journal and filesystem corruption >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-bugs >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: >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 [email protected]:/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: >Unformatted: _______________________________________________ [email protected] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "[email protected]"
