From owner-freebsd-current@FreeBSD.ORG  Sat Nov  1 00:33:10 2014
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 1030A372
 for <freebsd-current@freebsd.org>; Sat,  1 Nov 2014 00:33:10 +0000 (UTC)
Received: from smtp.des.no (smtp.des.no [194.63.250.102])
 by mx1.freebsd.org (Postfix) with ESMTP id C30B3BC5
 for <freebsd-current@freebsd.org>; Sat,  1 Nov 2014 00:33:09 +0000 (UTC)
Received: from nine.des.no (smtp.des.no [194.63.250.102])
 by smtp-int.des.no (Postfix) with ESMTP id 61443A253;
 Sat,  1 Nov 2014 00:33:08 +0000 (UTC)
Received: by nine.des.no (Postfix, from userid 1001)
 id E0CC8109F4; Sat,  1 Nov 2014 01:33:09 +0100 (CET)
From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= <des@des.no>
To: Manfred Antar <null@pozo.com>
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>
Date: Sat, 01 Nov 2014 01:33:09 +0100
In-Reply-To: <201410312231.s9VMVsT1002148@pozo.com> (Manfred Antar's message
 of "Fri, 31 Oct 2014 15:31:54 -0700")
Message-ID: <86fve392uy.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: Andreas Tobler <andreast-list@fgznet.ch>,
 Oliver Hartmann <ohartman@zedat.fu-berlin.de>,
 FreeBSD CURRENT <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
 <freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current/>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 01 Nov 2014 00:33:10 -0000

Manfred Antar <null@pozo.com> writes:
> Then for some reason /var started to being mounted mfs.
> so for me i think it has something to do with the new rc.d startup files.
> 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.

> Writing entropy file:random: unblocking device.
>
> takes a little longer=20
> I changed to entropy_save_sz=3D"4096"  in /etc/rc.conf, maybe thats why.

That shouldn't make any difference.  Our /dev/random never blocks once
it's seeded, and reading 4096 bytes won't take noticeably longer than
reading 2048 bytes.  But it should already be unblocked by then - this
is on shutdown, right?

DES
--=20
Dag-Erling Sm=C3=B8rgrav - des@des.no