From owner-freebsd-current@FreeBSD.ORG Fri Oct 31 20:04:58 2014 Return-Path: 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 7C208D87 for ; Fri, 31 Oct 2014 20:04:58 +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 39E4DA53 for ; Fri, 31 Oct 2014 20:04:57 +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 s9VK0AWB002147 (version=TLSv1/SSLv3 cipher=DHE-DSS-AES256-SHA bits=256 verify=NOT); Fri, 31 Oct 2014 13:00:11 -0700 (PDT) (envelope-from null@pozo.com) Message-Id: <201410312000.s9VK0AWB002147@pozo.com> X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9 Date: Fri, 31 Oct 2014 13:00:10 -0700 To: "O. Hartmann" , FreeBSD CURRENT From: Manfred Antar Subject: Re: CURRENT: WARNING! r273914 leaves filesystems in inconsistent/corrupted condition! In-Reply-To: <20141031202045.2e02f4a3.ohartman@zedat.fu-berlin.de> References: <20141031202045.2e02f4a3.ohartman@zedat.fu-berlin.de> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" 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: s9VK0AWB002147 X-pozocom-MailScanner: Found to be clean X-pozocom-MailScanner-From: null@pozo.com 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 20:04:58 -0000 At 12:20 PM 10/31/2014, O. Hartmann wrote: >On all CURRENT systems I updated today (31.10.2014) I had massive filesystem corruption >after reboot. The systems do have > >FreeBSD 11.0-CURRENT #1 r273914: Fri Oct 31 19:40:04 CET 2014 amd64 > >and suffer without exception from the same breakage, quitting services and/or reporting >corrupted filesystems after a fresh reboot - even if I've performed a manual triggered >"fsck -fz" in single user mode on the console. > >All systems have GPT partion schemes. > >The problem is serious! I can not get rid via fsck of the problem of corrupted >filesystems. Services like OpenLDAP (Slapd), nslcd, dbus, hal or postgresql do not start >properly and need to be started manually after a reboot. > >What is wrong? The fact that several CURRENT boxes are affected the very same way (> 5 ) >make me confident this is a serious bug recently introduced. > >Oliver > With r273911 on amd64, after fresh build installworld. Upon reboot all of a sudden /var is mounted mfs. needless to say many problems with programs that store files in /var -- ie mysql clamav etc, etc I had to change the following in rc.conf to get system to work again. varmfs="AUTO" # Set to YES to always create an mfs /var, NO to never varsize="32m" # Size of mfs /var if created varmfs_flags="-S" # Extra mount options for the mfs /var populate_var="AUTO" # Set to YES to always (re)populate /var, NO to never cleanvar_enable="YES" # Clean the /var directory CHANGED TO : varmfs="NO" # Set to YES to always create an mfs /var, NO to never varsize="32m" # Size of mfs /var if created varmfs_flags="-S" # Extra mount options for the mfs /var populate_var="NO" # Set to YES to always (re)populate /var, NO to never cleanvar_enable="NO" # Clean the /var directory Not why all of a sudden /var/ was mounted mfs. Maybe something to do with the new random stuff, I did a mergemaster before rebooting Not sure if this is related to your problem Manfred ======================== || null@pozo.com || || || ======================== -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.