From owner-freebsd-current@FreeBSD.ORG Fri Oct 31 22:32:29 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 CA31D662 for ; Fri, 31 Oct 2014 22:32:29 +0000 (UTC) Received: from pozo.com (pozo.com [50.197.129.137]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "pozo.com", Issuer "pozo.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 8C4DFDC7 for ; Fri, 31 Oct 2014 22:32:29 +0000 (UTC) Received: from T61p.pozo.com (t61p.pozo.com [192.168.0.4]) (authenticated bits=0) by pozo.com (8.14.9/8.14.9) with ESMTP id s9VMVsT1002148 (version=TLSv1/SSLv3 cipher=DHE-DSS-AES256-SHA bits=256 verify=NOT); Fri, 31 Oct 2014 15:31:55 -0700 (PDT) (envelope-from null@pozo.com) Message-Id: <201410312231.s9VMVsT1002148@pozo.com> X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9 Date: Fri, 31 Oct 2014 15:31:54 -0700 To: Andreas Tobler , Dag-Erling =?iso-8859-1?Q?Sm=C3=B8rgrav?= , Oliver Hartmann , Martin MATO From: Manfred Antar Subject: Re: CURRENT: WARNING! r273914 leaves filesystems in inconsistent/corrupted condition! In-Reply-To: <545402C9.4070901@fgznet.ch> References: <20141031202045.2e02f4a3.ohartman@zedat.fu-berlin.de> <86a94c9bn3.fsf@nine.des.no> <545402C9.4070901@fgznet.ch> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Spam-Status: No, score=-102.4 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00, MISSING_MID,URIBL_BLOCKED,USER_IN_WHITELIST autolearn=no autolearn_force=no version=3.4.0, No X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on pozo.com X-pozocom-MailScanner-Information: Please contact the ISP for more information X-pozocom-MailScanner-ID: s9VMVsT1002148 X-pozocom-MailScanner: Found to be clean X-pozocom-MailScanner-From: null@pozo.com Cc: FreeBSD CURRENT 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: Fri, 31 Oct 2014 22:32:29 -0000 At 02:44 PM 10/31/2014, Andreas Tobler wrote: >On 31.10.14 22:23, Dag-Erling Sm=C3=B8rgrav wrote: >>Can you all please tell me which revision(s) you were running before you >>upgraded? Something like "bzgrep 11.0-CURRENT /var/log/messages*" >>should do the trick. > >+1 here. 'Corrupted' /usr. Changed entry in fstab to not check fs. > >[zrhws131:/boot/kernel.old] andreast% strings kernel | grep CURRENT >@(#)FreeBSD 11.0-CURRENT #33 r273767M: Tue Oct 28 11:20:32 CET 2014 > >Andreas > > > FreeBSD 11.0-CURRENT #0 r273905: Fri Oct 31 06:15:56 PDT 2014 11.0-CURRENT No corruption here, during the last few days i was getting sysctl-random er= ror during boot. So today I did a buildworld installworld buildkernel installkernel, and mer= gemaster . some of the /etc/rc.d/random files were updated. Reboot 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. I noticed one thing during boot: 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. =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D || null@pozo.com || || || =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=20