From owner-freebsd-questions@freebsd.org Mon Dec 11 12:58:18 2017 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id AD58EE9123C for ; Mon, 11 Dec 2017 12:58:18 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mout.kundenserver.de (mout.kundenserver.de [217.72.192.74]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.kundenserver.de", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 0FF7063F3D for ; Mon, 11 Dec 2017 12:58:17 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from r56.edvax.de ([92.195.18.98]) by mrelayeu.kundenserver.de (mreue103 [212.227.15.183]) with ESMTPA (Nemesis) id 0MCfv0-1eF4Gd0Ieg-009MyI; Mon, 11 Dec 2017 13:58:05 +0100 Date: Mon, 11 Dec 2017 13:58:03 +0100 From: Polytropon To: freebsd@dreamchaser.org Cc: Adam Vande More , FreeBSD Questions Subject: Re: Subject: Thunderbird causing system crash, need guidance Message-Id: <20171211135803.d1aff6c8.freebsd@edvax.de> In-Reply-To: <38e2ef70-fa1b-25bf-4447-752006418d0a@dreamchaser.org> References: <201712110045.vBB0jCTQ078476@nightmare.dreamchaser.org> <38e2ef70-fa1b-25bf-4447-752006418d0a@dreamchaser.org> Reply-To: Polytropon Organization: EDVAX X-Mailer: Sylpheed 3.1.1 (GTK+ 2.24.5; i386-portbld-freebsd8.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:8EIRMBap8QtjzYPv2A6tMdM0BTuiDf0Z67zt91rUG4T+m1hGLxa SRPArkkNIkyS8usKZfpoUaM/U9Djcz2QD9Mynup9f70YyYc3MhB1pQWux5H0ohV+mEJy5NO e3eq+aVXZalbj9/PkT7/78FZ30fvSE5XvLEzYEFus6UxGjoNqoWNLy9+QuKqr6jceETE3t9 GoZO/8F+PREzoMgBf0R7w== X-UI-Out-Filterresults: notjunk:1;V01:K0:Ml4WeOBgtGo=:lHrqWMCtNaWzMAMNeNcXvg z8+/bjMTuLA23FPOBIiUA12aMpx27FklBDSB/Rcbw/wkjxLPr3er5QIvZc1Qy5CAkGDYwAjvm nA5TUXrr2Y54BoA1VEMFitu1nqVAvOyBHKbEgVlp8LdSSI9v31L2YVURTYGgJS5GTbM9pC37E BrGGio1uJRjAqYbR0m7uCxNcZcJNUlr8WEVz8Qb0hMptJx4AOl9zQwkOrr66za3MTcVytgMLL fmVL9Ftb8Ta77vkrqHRY/Id+FB5be5deIKS87Hi9Cq96r6TBTCyQZRTlUHX0QZ1BUrQt7XtpL udI9uErnG7ufEXfJ7CxD3K/VHLvMBD2pNN+dyymefv+6wgI4nBQSDrR8ET0w2/Mt2F6DvKoUl EnfGBjfVfXrOw4N4DEdZOBJKbH2uWajlzqgSE7APNYfKaQjl4yB6PapvW3Uc6g6HpbZ4Jtzae /YQyX+NOKGVOXy9yJv6c6FNbcWc6UAsSGFmSTaVd+7ld6noSuSTQr4bh29eb0XmjnnHufMbXi QxJGk1q5OQSHiIn7g+zf7WDMInVozxW07Qaw/lS+bmpgCfHtBrGlvH5JmBT+pVnIDGxMcE9xm sSTe/ehyEs6fozk5IQdqTjThaPbj9D1+ZC0PGQUw4mSlPqC3Ebl2ALo9chCPQ4zdEgkrXxq9V WZ1UPAqLVJ8OOuLvFRVwbEvO3Q3/+r8nFEGtlNzGEdbDNhKk+ICiab2D15lxc5lQXq4JY6fGj WxaREpRm+PtS73/9pM99Qx3ntx864NSI7o+cScI8bsm+7qFGT/lWz617WHQ= X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Dec 2017 12:58:18 -0000 On Sun, 10 Dec 2017 21:56:16 -0700, Gary Aitken wrote: > On 12/10/17 19:02, Adam Vande More wrote: > > On Sun, Dec 10, 2017 at 6:45 PM, Gary Aitken wrote: > > >> From fstab: > >> /dev/ufs/hd250G1root / ufs rw,noatime 1 1 > >> /dev/ufs/hd250G1var /var ufs rw,noatime 2 2 > >> /dev/ufs/hd250G1usr /usr ufs rw,noatime 7 3 > >> tmpfs /tmp tmpfs rw,mode=01777 0 0 > >> md99 none swap sw,file=/usr/swap/swap,late 0 0 > >> /var is 16G > >> > >> It seems like it may be corrupted disk data, but I'm wondering if > >> there's a good way to diagnose that. > > > > fsck(8) > > duh, thanks. > That did solve the problem. > > However, I'm confused. > Upon reboot, the system checks to see if file systems were properly > dismounted and is supposed to do an fsck. Since those don't show up > in messages, I can't verify this, but I'm pretty certain it must have > thought it was clean, which it wasn't. (One reason I'm pretty certain > is the time involved when run manually as you suggested). This is the primary reason for setting background_fsck="NO" in /etc/rc.conf - if you can afford a little downtime. The background fsck doesn't have all the repair capabilities a forced foreground check has, to it _might_ leave the file system in an inconsistent state, and the system runs with that unclean partition. > The file system in question was mounted below "/". > Does the system only auto-check file systems mounted at "/"? Yes, / is the first file system it checks. The two last fields in /etc/fstab control what fsck will check, and /etc/rc.conf allows additional flags for those automatic checks. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ...