From owner-freebsd-questions@freebsd.org Mon Dec 11 04:56:52 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 EEC4EE85F33 for ; Mon, 11 Dec 2017 04:56:52 +0000 (UTC) (envelope-from freebsd@dreamchaser.org) Received: from nightmare.dreamchaser.org (ns.dreamchaser.org [66.109.141.57]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id C450C713BC for ; Mon, 11 Dec 2017 04:56:52 +0000 (UTC) (envelope-from freebsd@dreamchaser.org) Received: from breakaway.dreamchaser.org (breakaway [192.168.151.122]) by nightmare.dreamchaser.org (8.15.2/8.15.2) with ESMTP id vBB4umLP090638; Sun, 10 Dec 2017 21:56:50 -0700 (MST) (envelope-from freebsd@dreamchaser.org) Subject: Re: Subject: Thunderbird causing system crash, need guidance To: Adam Vande More , FreeBSD Questions References: <201712110045.vBB0jCTQ078476@nightmare.dreamchaser.org> Reply-To: freebsd@dreamchaser.org From: Gary Aitken Message-ID: <38e2ef70-fa1b-25bf-4447-752006418d0a@dreamchaser.org> Date: Sun, 10 Dec 2017 21:56:16 -0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.6.2 (nightmare.dreamchaser.org [192.168.151.101]); Sun, 10 Dec 2017 21:56:50 -0700 (MST) 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 04:56:53 -0000 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). The file system in question was mounted below "/". Does the system only auto-check file systems mounted at "/"? > Your swap configuration is also mostly likely silly. If you need > more performance, that's not the way to do it. Can you explain or point me to an explanation for this comment? It looks to me like what's shown in the EXAMPLES section of "man fstab". Thanks, Gary