Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!uunet!pdn!boake2!sherpa!rac
From: rac@sherpa.uucp (Roger Cornelius)
Newsgroups: comp.unix.xenix
Subject: /u doesn't get fsck'd or mounted during boot
Keywords: fsck /u 2.3.2 286
Message-ID: <183@sherpa.uucp>
Date: 28 Nov 89 00:36:28 GMT
Organization: Personal System Computing,  St. Petersburg, FL
Lines: 38

Since installing the 2.2.? -> 2.3.2 upgrade for the 286, my /u
filesystem doesn't get fsck'd during the boot sequence.  This happens
whether /u is dirty, or I specified "fsck=yes" in /etc/default/filesys
according to the man page for mnt(C).  (the filesys(F) man page doesn't
mention the "fsck" keyword, only "fsckflags".)
If I understand correctly, when "fsck=yes" is specified the
filesystem is fsck'd regardless of whether it's dirty or not.

If the /u filesystem is dirty, the mount command just fails and
returns:
  mount: mount failed
  mount: Structure needs cleaning
  Failed to mount /u filesystem

mount is invoked from /etc/rc.d/2/mntfs with the following command:
  eval mnt -rc $AUTOFLAG $AUTOBOOT

I had this working in 2.2.3, and I think I have things set up
correctly now also.  Can someone tell me if I've just missed
something, or is this a bug?

Following are my /etc/default/filesys and /etc/fstab files:
# /etc/default/filesys
bdev=/dev/root cdev=/dev/rroot \
    mountdir=/ mount=no mountflags= \
    fsck=no fsckflags= \
    desc="The root filesystem" \
    rcmount=no rcfsck=no
bdev=/dev/u mountdir=/u rcmount=yes \
    fsckflags="-y -t /dev/scratch"

# /etc/fstab
/dev/u /u fsckflags="-y -D -t /dev/scratch"

Thanks for any suggestions.

--
Roger A. Cornelius           rac@sherpa            uunet!sherpa!rac