Date: Mon, 4 Oct 2004 18:47:08 +0300 From: Ion-Mihai Tetcu <itetcu@people.tecnik93.com> To: Brooks Davis <brooks@one-eyed-alien.net> Cc: freebsd-current@freebsd.org Subject: Re: /dev/md0 keeps mounting on /var Message-ID: <20041004184708.248efdd8@it.buh.tecnik93.com> In-Reply-To: <20041004153257.GA30883@odin.ac.hmc.edu> References: <20041004173545.3af254c6@it.buh.tecnik93.com> <20041004153257.GA30883@odin.ac.hmc.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 4 Oct 2004 08:32:57 -0700 Brooks Davis <brooks@one-eyed-alien.net> wrote: > 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 ? >=20 > 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. No, it is not the case. Does the order in fstab meter ?=20 /dev/ad0s3d is already mountrd on /var when md0 bumps in. >From memory it looks like this: % mount /dev/ad0s3a on / (ufs, local) devfs on /dev (devfs, local) /dev/ad0s3f on /tmp (ufs, local, soft-updates) /dev/ad0s3d on /var (ufs, local, soft-updates) /dev/ad0s3e on /usr (ufs, local, soft-updates) /dev/ad0s2d on /home (ufs, local, soft-updates) /dev/ad0s4 on /vol/it/xp (msdosfs, local, read-only) /dev/ad1s3d on /vol/it/cur/h (ufs, local, soft-updates) /dev/ad1s2d on /vol/it/n (ufs, local, soft-updates) devfs on /var/named/dev (devfs, local) /dev/md0 on /var (ufs, local, soft-updates) > 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?=20 > You can try setting varmfs=3D"NO" and populate_var=3D"NO" in /etc/rc.conf > to disable this script. #cat /etc/fstab # Device Mountpoint FStype Options Dump Pas= s# /dev/ad0s2b none swap sw 0 0 #/dev/ad1s1b none swap sw 0 0 /dev/ad0s3a / ufs rw 1 1 /dev/ad0s3f /tmp ufs rw 2 2 /dev/ad0s3d /var ufs rw 2 2 /dev/ad0s3e /usr ufs rw 2 2 /dev/ad0s2d /home ufs rw, 2 2 /dev/ad0s4 /vol/it/xp msdosfs ro 0 1 # bk #/dev/ad0s1d /vol/it/cur/d ufs rw,noauto 2 2 #/dev/ad0s1e /vol/it/cur/e ufs rw,noauto 2 2 #160WD /dev/ad1s3d /vol/it/cur/h ufs rw 2 2 #/dev/ad1s1e /vol/it/m ufs rw 2 2 /dev/ad1s2d /vol/it/n ufs rw 2 2 /dev/cd0 /home/itetcu/cdrom cd9660 ro,noauto,nodev,nosuid = 0 0 /dev/cd1 /home/itetcu/cdrom1 cd9660 ro,noauto,nodev,nosuid = 0 0 Thanks for your help, --=20 IOnut Unregistered ;) FreeBSD "user"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20041004184708.248efdd8>