Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!agate!howland.reston.ans.net!europa.eng.gtefsd.com!uunet!news.univie.ac.at!fstgds15.tu-graz.ac.at!fstgds01.tu-graz.ac.at!not-for-mail From: chmr@edvz.tu-graz.ac.at (Christoph Robitschko) Newsgroups: comp.os.386bsd.questions Subject: Re: what is fs_clean for? Date: 12 Oct 1993 08:56:22 +0100 Organization: Technical University of Graz, Austria Lines: 23 Distribution: world Message-ID: <29dnv6INNbtq@fstgds01.tu-graz.ac.at> References: <BLYMN.93Oct3175636@mallee.awadi.com.au> <29c2q9$32v@alva.ge.com> NNTP-Posting-Host: fstgds01.tu-graz.ac.at X-Newsreader: TIN [version 1.2 PL1] In article <29c2q9$32v@alva.ge.com> Stephen F. Combs (steve@@salem.ge.com) wrote: > Not to sound pedantic, or start a flame-war, BUT you should NEVER mount > a filesystem which is suspect UNTIL you have cleaned it up. I've seen > too many times when a system will barf at the LEAST acceptable time if you > attempt to bypass stability checks. There are exceptions to this, for example if you know fsck can't clean up the filesystem, and you want to get some data off the filesystem before you re-initialize it. On the other hand, I also don't want the system to panic because I mounted a dirty filesystem, and I did not even get a warning that the filesystem was dirty. So, IMHO: mount /dev/sd0g /usr should not work if the filesystem is dirty. mount -F ... should do it (-f is already taken for -fake). fsck should set the filesystem to clean state. umount should set the filesystem to clean state if it was clean when mounted. Christoph