Date: Sat, 01 Nov 2014 01:33:09 +0100 From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= <des@des.no> To: Manfred Antar <null@pozo.com> Cc: Andreas Tobler <andreast-list@fgznet.ch>, Oliver Hartmann <ohartman@zedat.fu-berlin.de>, FreeBSD CURRENT <freebsd-current@freebsd.org> Subject: Re: CURRENT: WARNING! r273914 leaves filesystems in inconsistent/corrupted condition! Message-ID: <86fve392uy.fsf@nine.des.no> In-Reply-To: <201410312231.s9VMVsT1002148@pozo.com> (Manfred Antar's message of "Fri, 31 Oct 2014 15:31:54 -0700") References: <20141031202045.2e02f4a3.ohartman@zedat.fu-berlin.de> <86a94c9bn3.fsf@nine.des.no> <545402C9.4070901@fgznet.ch> <201410312231.s9VMVsT1002148@pozo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?86fve392uy.fsf>