Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!elroy.jpl.nasa.gov!usc!howland.reston.ans.net!pipex!uknet!mcsun!sun4nl!philapd!apdnews!spoetnix.idca.tds.philips.nl!wilko From: wilko@idca.tds.philips.nl (Wilko Bulte) Newsgroups: comp.os.386bsd.questions Subject: Re: what is fs_clean for? Message-ID: <wilko.749384609@spoetnix.idca.tds.philips.nl> Date: 30 Sep 93 10:23:29 GMT References: <28da76$fhf@acsc.com> Sender: news@idca.tds.philips.nl Lines: 24 jerry@acsc.com (Jerry Chen) writes: >In the superblock of UFS, there are two fields: >ufs/fs.h: char fs_clean; /* file system is clean flag */ >ufs/fs.h: long fs_state; /* validate fs_clean field */ >My guess is that they are used to determine if the file system is clean, ie, umounted >successfully. And if the file system is clean, we do not need to fsck it since >life is too short to always run fsck. You're guess is right. SysV uses this since ages (?), so does DEC OSF/1, which uses the ufs filesystem. fsck -p checks if the fs is clean, and skips it if it is. You need to modify both fsck, (u)mount in the ufs code. I've been thinking about it myself, and it should not be a big issue I think. Haven't found time to do it myself. Wilko -- | / o / / _ Wilko Bulte mail: wilko@idca.tds.philips.nl |/|/ / / /( (_) |d|i|g|i|t|a|l| Equipment Corporation voice: +3155-432062 fax: +3155-432103 DTN: 829 2062 PO Box 245 - 7300 AE Apeldoorn - The Netherlands