/dev/md0 keeps mounting on /var

Brooks Davis brooks at one-eyed-alien.net
Mon Oct 4 09:00:10 PDT 2004

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.

-- Brooks

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
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-current/attachments/20041004/336ee235/attachment.bin

More information about the freebsd-current mailing list