Date: Mon, 28 Aug 1995 18:04:42 -0400 From: Coranth Gryphon <shaman@mv.MV.COM> To: hackers@freebsd.org Message-ID: <199508282204.SAA25516@mv.mv.com>
next in thread | raw e-mail | index | archive | help
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: Re: FreeBSD2.0 Clean Flag in Superblock
References: <41bl3c$81q@mippet.ci.com.au> <41e49a$3lm@reason.cdrom.com> <41j96n$1nq@taxis.corp.titan.com> <ALAN.95Aug27233916@parsley.lcs.mit.edu>
Organization: MV Communications, Inc.
Alan Bawden <alan@lcs.mit.edu> wrote:
>In article <41j96n$1nq@taxis.corp.titan.com>
>ss@tisc.com (Steve Schossow) writes:
>
> "Jordan K. Hubbard" <jkh@FreeBSD.org> wrote:
> >Neither did we, which is why that fsck is no longer in there... :-)
>
> 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!
Is it that difficult to have a clopt that suppresses the "CLEAN FLAG"
message, but tells you about everything else? I did a quick patch
and my version seems to work fine.
Anyone have a reason for this patch to be a bad thing?
Anyone want it (ie. to fold back into the distribution)?
-coranth
--------------------------------------------------------+----------------------
Coranth Gryphon | Reality exists on a
| need-to-know basis.
E-Mail: gryphon@healer.com, shaman@mv.mv.com |
Pager: (603) 599-0357 Phone: (603) 598-3440 | You do not currently
US-Mail: 11 Carver Street, Nashua, NH 03060-2518 | need to know
Disclaimer: All these words are yours, except Europa... +----------------------
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199508282204.SAA25516>