Date: Tue, 12 Dec 2017 12:54:05 -0600 From: Adam Vande More <amvandemore@gmail.com> To: freebsd@dreamchaser.org Cc: Polytropon <freebsd@edvax.de>, FreeBSD Questions <freebsd-questions@freebsd.org> Subject: Re: Subject: Thunderbird causing system crash, need guidance Message-ID: <CA%2BtpaK3trYoJJXgv_r%2BqSD3Pr0g=3kTATyBShYFFWGLDpdRQdA@mail.gmail.com> In-Reply-To: <5fbcd05c-ce12-b1a4-a9e9-79276dad7183@dreamchaser.org> References: <201712110045.vBB0jCTQ078476@nightmare.dreamchaser.org> <CA%2BtpaK0sG31TckxL8orNmAD0ZXSz7rJzEotjsCEtASw9u2COZg@mail.gmail.com> <38e2ef70-fa1b-25bf-4447-752006418d0a@dreamchaser.org> <20171211135803.d1aff6c8.freebsd@edvax.de> <5fbcd05c-ce12-b1a4-a9e9-79276dad7183@dreamchaser.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Dec 12, 2017 at 12:30 PM, Gary Aitken <freebsd@dreamchaser.org> wrote: > > The ordering part I understand; what I don't understand is why it (as I > recall) rebooted successfully with no warnings in spite of the > background_fsck="NO" being set and when one of the disks apparently > didn't fsck properly. I thought it should have halted in single-user > mode and waited for me to do a full fsck manually. That happens if the preen fails. See the man page I pointed you to. There are cases where it can miss things. You can set: fsck_y_enable="YES" If you want it to handle a failed preen automatically. I don't think background fsck presence or lack of had much to do with this. It is a popular whipping boy. A regular foreground fsck may not be a bad idea if your system is prone disk errors or hard crashes. Perhaps sysutils/diskcheckd or a periodic entry, but under *normal* circumstances such things are not needed. -- Adam
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CA%2BtpaK3trYoJJXgv_r%2BqSD3Pr0g=3kTATyBShYFFWGLDpdRQdA>