From owner-freebsd-questions@FreeBSD.ORG Sun Aug 10 12:30:34 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 EC0A1C48 for ; Sun, 10 Aug 2014 12:30:34 +0000 (UTC) Received: from mail-wg0-x22d.google.com (mail-wg0-x22d.google.com [IPv6:2a00:1450:400c:c00::22d]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 84AB82E35 for ; Sun, 10 Aug 2014 12:30:34 +0000 (UTC) Received: by mail-wg0-f45.google.com with SMTP id x12so7336239wgg.4 for ; Sun, 10 Aug 2014 05:30:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20120113; h=date:from:to:subject:message-id:in-reply-to:references:mime-version :content-type:content-transfer-encoding; bh=Ts86rPr6gA9ohnK8f79MMTbgzyq/EuQh8tUxLZ1VwCg=; b=BNSUmPbSoHvLcPWg86JpHkDJUSdpQW34TvsmdzXN+hERBWASIJUYGPVvU4ZT+6sdfg Q26sAm8IsnxAjDd8LU/GkO1LgWX0OXtGPTwNwPIXs8nF9osy20+p/DpHNHy9UGesoWp/ hzazdXcTYxASGj40ZLeTMEWaMLcS6QPTC2cRYMWoS5u6pQQUef4ccM3oyxhgIi3P4ZdV aM0MLA575dBujuAXxCQhTr2EVBTWjg+4c7xscZ3xOrRaENSswJN24oV36ZgMUFe/Mvv7 WYzGptnikjCScqwlWVOaH8tLCvCm8/Gw9GilhPNA4z3sMpuPwmLmIJ4YiHVIlSTJA9Kc mA2A== X-Received: by 10.180.210.163 with SMTP id mv3mr17480080wic.15.1407673832482; Sun, 10 Aug 2014 05:30:32 -0700 (PDT) Received: from gumby.homeunix.com (5ec2dc78.skybroadband.com. [94.194.220.120]) by mx.google.com with ESMTPSA id ex2sm31769152wjd.30.2014.08.10.05.30.31 for (version=SSLv3 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 10 Aug 2014 05:30:31 -0700 (PDT) Date: Sun, 10 Aug 2014 13:30:30 +0100 From: RW To: freebsd-questions@freebsd.org Subject: Re: operation not permitted on entropy file Message-ID: <20140810133030.1eb5d617@gumby.homeunix.com> In-Reply-To: <20140810124433.da498898.freebsd@edvax.de> References: <20140810070239.GA80734@home.parts-unknown.org> <20140810103119.GA26958@slackbox.erewhon.home> <20140810124433.da498898.freebsd@edvax.de> X-Mailer: Claws Mail 3.10.1 (GTK+ 2.24.22; amd64-portbld-freebsd10.0) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit 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:30:35 -0000 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.