From owner-freebsd-current@FreeBSD.ORG Sat Nov 1 14:21:56 2014 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 70B8E143 for ; Sat, 1 Nov 2014 14:21:56 +0000 (UTC) Received: from smtp.des.no (smtp.des.no [194.63.250.102]) by mx1.freebsd.org (Postfix) with ESMTP id 2F62AC89 for ; Sat, 1 Nov 2014 14:21:55 +0000 (UTC) Received: from nine.des.no (smtp.des.no [194.63.250.102]) by smtp-int.des.no (Postfix) with ESMTP id DEBC6ADBF; Sat, 1 Nov 2014 14:21:46 +0000 (UTC) Received: by nine.des.no (Postfix, from userid 1001) id 2B12110A69; Sat, 1 Nov 2014 15:21:48 +0100 (CET) From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= To: Tomoaki AOKI Subject: Re: CURRENT: WARNING! r273914 leaves filesystems in inconsistent/corrupted condition! References: <20141031202045.2e02f4a3.ohartman@zedat.fu-berlin.de> <86a94c9bn3.fsf@nine.des.no> <545402C9.4070901@fgznet.ch> <201410312231.s9VMVsT1002148@pozo.com> <86fve392uy.fsf@nine.des.no> <20141101153554.77a4a7e4cef7bfe2b9486e89@dec.sakura.ne.jp> Date: Sat, 01 Nov 2014 15:21:48 +0100 In-Reply-To: <20141101153554.77a4a7e4cef7bfe2b9486e89@dec.sakura.ne.jp> (Tomoaki AOKI's message of "Sat, 1 Nov 2014 15:35:54 +0900") Message-ID: <86y4rv6lxf.fsf@nine.des.no> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 01 Nov 2014 14:21:56 -0000 Tomoaki AOKI writes: > Dag-Erling Sm=C3=B8rgrav writes: > > Manfred Antar writes: > > > Then for some reason /var started to being mounted mfs. [...] If > > > I have varmfs=3D"NO" and cleanvar_enable=3D"NO" everything works fine. > > Not really. The default for varmfs is AUTO, which mounts a memory > > file system on /var if, after mounting all "early" file systems, > > /var is not writeable. > For me, Manfred's workaround actually helped. It helped that particular issue, more or less by accident. It was not in any way a correct fix or even a correct workaround. > In single user mode, actual /var (in root partition) appears as > before. So there can be some mis-ordering within rc scripts. > (Remounting of / is delayed? Check for /var too early?) Exactly right; the check for a writeable /var occurred before / was mounted r/w, so it mounted an mfs instead. Xin fixed this in r273919. > For me, [unblocking /dev/random] takes nearly 2 minutes each boot > after r273872. No specific rc.conf setting for it. That means we're not getting enough entropy during early boot, or we're underestimating the amount of entropy we're getting. We added entropy harvesting to device_attach() about a year ago, which in most cases provides enough entropy to unblock /dev/random before we even run init(8). DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no