Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!simtel!hookup!ames!olivea!grapevine.lcs.mit.edu!grapevine.lcs.mit.edu!alan From: alan@lcs.mit.edu (Alan Bawden) Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: FreeBSD2.0 Clean Flag in Superblock Date: 27 Aug 95 23:39:16 Organization: ITS Preservation Society Lines: 24 Message-ID: <ALAN.95Aug27233916@parsley.lcs.mit.edu> References: <41bl3c$81q@mippet.ci.com.au> <41d905$35v@blob.best.net> <41e49a$3lm@reason.cdrom.com> <41j96n$1nq@taxis.corp.titan.com> NNTP-Posting-Host: parsley.lcs.mit.edu In-reply-to: ss@tisc.com's message of Fri, 25 Aug 1995 01:32:08 GMT In article <41j96n$1nq@taxis.corp.titan.com> ss@tisc.com (Steve Schossow) writes: "Jordan K. Hubbard" <jkh@FreeBSD.org> wrote: >dillon@best.com (Matt Dillon) wrote: >> I've never quite understood why that fsck is in there. At best you >> would get information on the fragmentation on the drive out of it. >Neither did we, which is why that fsck is no longer in there... :-) [ Story deleted. ] My point being that running fsck -n and piping the output through grep could catch an impending problem if one picks the 'serious' messages. This story exactly parallels my own experience with a slowly failing disk drive on a FreeBSD 1.1 machine. It was extremely useful to have that early warning from the nightly fsck letting me know I was about to lose. I haven't upgraded beyond 2.0 yet, but when I do, you can be sure I'm going to put that fsck -back- in my /etc/daily! -- Alan Bawden Alan@LCS.MIT.EDU 617/492-7274 06BF9EB8FC4CFC24DC75BDAE3BB25C4B