rac@sherpa.uucp (Roger Cornelius) (11/28/89)
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
phil@lgnp1.LS.COM (Phil Eschallier) (11/28/89)
In article <183@sherpa.uucp> rac@sherpa.uucp (Roger Cornelius) writes: >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. > actually you need "rcfsck=yes" for cleaning during booting. i have posted before that the "rcfsck=dirty" does not work for 2.3.2 ('286). sco has said nothing. if you you get any help from them, please let me know. i have called sco and checked the sosco system -- there is no fix available yet. phil eschallier phil@ls.com btw -- please no flames for posting a "mail-type" response, this is to give sco another prompt.