From owner-freebsd-current@FreeBSD.ORG Sat Nov 1 06:36:05 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 581B3A99 for ; Sat, 1 Nov 2014 06:36:05 +0000 (UTC) Received: from dec.sakura.ne.jp (dec.sakura.ne.jp [210.188.226.8]) (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 E6CF7C33 for ; Sat, 1 Nov 2014 06:36:04 +0000 (UTC) Received: from fortune.joker.local (180-198-225-68.nagoya1.commufa.jp [180.198.225.68]) (authenticated bits=0) by dec.sakura.ne.jp (8.14.3/8.14.2/[SAKURA-WEB]/20080708) with ESMTP id sA16Zu54046685 for ; Sat, 1 Nov 2014 15:35:56 +0900 (JST) (envelope-from junchoon@dec.sakura.ne.jp) Date: Sat, 1 Nov 2014 15:35:54 +0900 From: Tomoaki AOKI To: freebsd-current@freebsd.org Subject: Re: CURRENT: WARNING! r273914 leaves filesystems in inconsistent/corrupted condition! Message-Id: <20141101153554.77a4a7e4cef7bfe2b9486e89@dec.sakura.ne.jp> In-Reply-To: <86fve392uy.fsf@nine.des.no> 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> Organization: Junchoon corps X-Mailer: Sylpheed 3.4.2 (GTK+ 2.24.22; amd64-portbld-freebsd10.0) Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-2022-JP Content-Transfer-Encoding: 7bit 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 06:36:05 -0000 On Sat, 01 Nov 2014 01:33:09 +0100 Dag-Erling Sm〓rgrav wrote: > Manfred Antar 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="NO" and cleanvar_enable="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. VirtualBox VM [head, r273922, amd64] on stable/10 host [r273847, amd64]. In my case, /var is NOT a mount point (root only partition, mounted rw), but empty mfsvar is forcibly used without Manfred's workaround in multi user mode. 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?) > > Writing entropy file:random: unblocking device. > > > > takes a little longer > > I changed to entropy_save_sz="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? For me, it takes nearly 2 minutes each boot after r273872. No specific rc.conf setting for it. > > DES > -- > Dag-Erling Sm〓rgrav - des@des.no > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" -- 青木 知明 [Tomoaki AOKI] junchoon@dec.sakura.ne.jp MXE02273@nifty.com