/dev/md0 keeps mounting on /var

[Ion-Mihai Tetcu]

On Mon, 4 Oct 2004 09:04:53 -0700
Brooks Davis <brooks at one-eyed-alien.net> wrote:

> On Mon, Oct 04, 2004 at 06:47:08PM +0300, Ion-Mihai Tetcu wrote:
> > On Mon, 4 Oct 2004 08:32:57 -0700
> > Brooks Davis <brooks at 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´t use it I suppose I´ve done something wrong with mergemaster.
> > > > 
> > > > The only workaround I´ve found is to rename /boor/kernel/g_md.ko.
> > > > 
> > > > And since I just can´t 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.
> > 
> > No, it is not the case. Does the order in fstab meter ? 
> > /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)
> 
> Weird.  Order shouldn't matter.  The code in the var script is really
> simple.  It creates the md file system if you have varmfs="YES" or if
> "/bin/mkdir -p /var/.diskless" fails.  Hmm, I just noticed that ru never
> MFC'd the fix to add -p to that command.  Do you have a /var/.diskless
> on /dev/ad0s3d?  If so, that's probably the problem.

No varmfs="YES"  but indeed I have /var/.diskless; I wonder where did it
came from, I don´t remember a crash on boot. What I do remember sometime
around beta4 is mdconfig failing each next boot, so maybe that is how
it got there.

I´ll remove it and post if the problem doesn´t go away.


Thanks,

-- 
IOnut
Unregistered ;) FreeBSD "user"