From owner-freebsd-questions@FreeBSD.ORG Sun Aug 10 12:42:12 2014 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 935CAF65 for ; Sun, 10 Aug 2014 12:42:12 +0000 (UTC) Received: from mx01.qsc.de (mx01.qsc.de [213.148.129.14]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 557532FDF for ; Sun, 10 Aug 2014 12:42:11 +0000 (UTC) Received: from r56.edvax.de (port-92-195-111-1.dynamic.qsc.de [92.195.111.1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx01.qsc.de (Postfix) with ESMTPS id 0BF2F3CBE6; Sun, 10 Aug 2014 14:42:02 +0200 (CEST) Received: from r56.edvax.de (localhost [127.0.0.1]) by r56.edvax.de (8.14.5/8.14.5) with SMTP id s7ACg2hH004653; Sun, 10 Aug 2014 14:42:02 +0200 (CEST) (envelope-from freebsd@edvax.de) Date: Sun, 10 Aug 2014 14:42:02 +0200 From: Polytropon To: RW Subject: Re: operation not permitted on entropy file Message-Id: <20140810144202.2eda9b24.freebsd@edvax.de> In-Reply-To: <20140810133030.1eb5d617@gumby.homeunix.com> References: <20140810070239.GA80734@home.parts-unknown.org> <20140810103119.GA26958@slackbox.erewhon.home> <20140810124433.da498898.freebsd@edvax.de> <20140810133030.1eb5d617@gumby.homeunix.com> 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 Cc: freebsd-questions@freebsd.org X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 10 Aug 2014 12:42:12 -0000 On Sun, 10 Aug 2014 13:30:30 +0100, RW wrote: > On Sun, 10 Aug 2014 12:44:33 +0200 > Polytropon wrote: > > > Allow me a small additional statement: > > > > On Sun, 10 Aug 2014 12:31:19 +0200, Roland Smith wrote: > > > If a filesystem isn't dismounted properly (e.g. because of a > > > crash), you should get a warning during the next boot. And the > > > system would run a filesystem check in "preen" mode (see fsck(8)). > > > If it finds serious errors that cannot be repaired in preen mode, > > > you should get an error message. > > > > The problem is: When you do _not_ have > > > > background_fsck="NO" > > > > in /etc/rc.conf, all this happens in background, and soon you're > > in XDM and your X session, so you don't get the error message. > > Still the system continues booting and working "normally" for > > the price of "silent" file system corruption. > > > > In my opinion, this setting should be the default. It's better > > to have a delay in the boot process, or a _stop_ of the boot > > process in case a severe file system damage has been detected. > > I also think it's more important to know about this fact than > > it is to quickly be guided into a "comfortable environment" > > that makes you believe everything is okay, while in fact it > > isn't. > > > > This kind of operation also makes sure that you can get aware > > of the "please re-run fsck" message in case a second pass is > > required. In the end, you get "file system marked clean", and > > only _now_ you know that things are okay. > > It's not quite as bad as that. The background fsck is only intended to > recover lost space. If it encounters an actual error, it marks the > filesystem with a flag that causes a foreground check on the next boot. Yes - at _next_ boot. And for performing file system checks, it first creates a snapshot. I think I'm the 0.000001% person who got his foot shot because of strange side effects. :-) (And I also lost files due to "too much automatism", but could regain the data; "fsck -yf" isn't always fist choice: "inode corrected" - file present, size 0, data gone.) As much as I like the fast booting process of FreeBSD: In case of something being wrong with the file system, I rather have the time to wait for a full fsck run (can require several minutes on bigger disks) than booting into a "halfway somehow snapshotted partially clean but good-looking" environment. :-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ...