https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=224347
Bug ID: 224347
Summary: Boot erroneously mounts severely damaged ufs file
system
Product: Base System
Version: 10.3-RELEASE
Hardware: Any
OS: Any
Status: New
Severity: Affects Some People
Priority: ---
Component: bin
Assignee: [email protected]
Reporter: [email protected]
If a non-system ufs file system is severely damaged and does not pass the
normal boot-time fsck -p sequence, it may still be mounted read-write and the
system will boot up into multi-user mode. This happens in spite of having
background_fsck="NO" in rc.conf. There are no messages posted to the system
log, and the console boot-time errors may have scrolled beyond reach in the
buffer if one logs into vt0. After the first reboot, there are no errors
related to the disk in question posted at boot-time.
This happens because the return value of checkfilesys in fsck_ffs/main.c is
basically ignored.
When this condition occurs, it is 100% repeatable. One can crash the system
and it will reboot as if everything is ok; running whatever software tweaks the
file system (in my case thunderbird) will always recrash the system.
See the discussion on freebsd-questions:
Subject: Thunderbird causing system crash, need guidance
--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
[email protected] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "[email protected]"
