Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!news.mira.net.au!yarrina.connect.com.au!news.mel.connect.com.au!munnari.OZ.AU!news.ecn.uoknor.edu!paladin.american.edu!gatech!newsfeed.internetmci.com!xmission!news.cc.utah.edu!news From: Brad Midgley <brad@pht.com> Newsgroups: comp.unix.bsd.freebsd.misc Subject: annoyance: CLEAN flag not being set Date: Fri, 12 Jan 1996 09:13:56 -0700 Organization: Pacific HiTech Inc. Lines: 32 Message-ID: <30F688C4.D8AAB72@pht.com> NNTP-Posting-Host: weevil.pht.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Mailer: Mozilla 2.0b4 (X11; I; Linux 1.3.56 i586) hi, I have several drives that are mounted read-only on boot, changed to read-write occasionally, but then set back to read-only whenever possible. The problem is, if the system crashes, even if the drives were read-only at the time of the crash, fsck checks them on reboot. It complains the CLEAN flag wasn't set. This is one of the /etc/fstab lines: /dev/sd1a /home/ftp/.1 ufs ro 1 2 (I changed the last '2' from a '1' and haven't observed a crash since then to see if the behavior is any different.) to make it writable: mount -o update,rw /dev/sd1a /home/ftp/.1 and back to r/o: mount -o upadate,ro /home/ftp/.1 The big pain here is I have 8 of these drives (on 2 controllers) and at 4 gigabytes each, waiting for fsck to check them all adds up to a lot of downtime. Is this a o.s. problem or something I'm doing wrong with fstab? running 2.1R on a p5/60 w/72M ram. -- brad@pht.com http://www.pht.com/~brad