From owner-freebsd-current@FreeBSD.ORG Mon Oct 4 15:28:10 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E385716A4DD for ; Mon, 4 Oct 2004 15:28:10 +0000 (GMT) Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id C3D8643D48 for ; Mon, 4 Oct 2004 15:28:10 +0000 (GMT) (envelope-from brdavis@odin.ac.hmc.edu) Received: from odin.ac.hmc.edu (localhost.localdomain [127.0.0.1]) by odin.ac.hmc.edu (8.13.0/8.13.0) with ESMTP id i94FWvPk005176; Mon, 4 Oct 2004 08:32:58 -0700 Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.13.0/8.13.0/Submit) id i94FWvOv005175; Mon, 4 Oct 2004 08:32:57 -0700 Date: Mon, 4 Oct 2004 08:32:57 -0700 From: Brooks Davis To: Ion-Mihai Tetcu Message-ID: <20041004153257.GA30883@odin.ac.hmc.edu> References: <20041004173545.3af254c6@it.buh.tecnik93.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="4Ckj6UjgE2iN1+kY" Content-Disposition: inline In-Reply-To: <20041004173545.3af254c6@it.buh.tecnik93.com> User-Agent: Mutt/1.4.1i X-Virus-Scanned: by amavisd-new X-Spam-Status: No, hits=0.0 required=8.0 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on odin.ac.hmc.edu cc: freebsd-current@freebsd.org Subject: Re: /dev/md0 keeps mounting on /var X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.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: Mon, 04 Oct 2004 15:28:11 -0000 --4Ckj6UjgE2iN1+kY Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Oct 04, 2004 at 05:35:45PM +0300, Ion-Mihai Tetcu wrote: > For some time I keep getting /dev/md0 mounting on /var as the last mount > when going to multi-user. The obvious result is that all services that > use /var fail to start/function properly. Since I don=B4t use it I > suppose I=B4ve done something wrong with mergemaster. >=20 > The only workaround I=B4ve found is to rename /boor/kernel/g_md.ko. >=20 > And since I just can=B4t fix this since ~ beta4 could someone point me > where to look ? This is proably happening because your /var is failing the writability test in /etc/rc.d/var. One situation I can of where this could happen and you would otherwise have a valid /var would be if you have a read-only NFS root and an NFS /var. In that cause /var wouldn't be mounted yet because mountcritremote wouldn't be run yet. Is this or something similar the case for you? You can try setting varmfs=3D"NO" and populate_var=3D"NO" in /etc/rc.conf to disable this script. -- Brooks --=20 Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 --4Ckj6UjgE2iN1+kY Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFBYW0pXY6L6fI4GtQRAkHsAKCWJGsbugd9A5laGVPvKX1I82tNxACgnzwf GXiN20wtUNZTOln+Y7cQac0= =GuPd -----END PGP SIGNATURE----- --4Ckj6UjgE2iN1+kY--