From owner-freebsd-current  Sun Mar  5 18:46:13 1995
Return-Path: current-owner
Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id SAA18618 for current-outgoing; Sun, 5 Mar 1995 18:46:13 -0800
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.34]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id SAA18612 for <freebsd-current@FreeBSD.org>; Sun, 5 Mar 1995 18:46:06 -0800
Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id MAA10741; Mon, 6 Mar 1995 12:43:09 +1000
Date: Mon, 6 Mar 1995 12:43:09 +1000
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199503060243.MAA10741@godzilla.zeta.org.au>
To: freebsd-current@FreeBSD.org, j@uriah.heep.sax.de
Subject: Re: any news for gdb?
Sender: current-owner@FreeBSD.org
Precedence: bulk

>I've just accidentally started gdb and being caught by the `usual'
>panic.  But i've been rather surprised, remembering back, that gdb

I thought that this was fixed, although the commit message said it
probably isn't.

>I also noticed (this was with a 950210-SNAP kernel) that the fsck -p
>did not complain about any inconsistencies in the file system other
>than the statistics, but it *silently* truncated my files to zero
>length.  Sounds like a bug to me.  (Previously i remember that i've
>seen something like ``Incorrect block count, 4 should be 0 (fixed)''
>in this case, which was a clear signal to not trust the files.)

I haven't noticed this.  I've noticed that the sync() in boot() now
_always_ fails.  It has been doing this since the first or second
partial fix to the disk "chattering" bug.  Usually there are 3
unflushable buffers.  fsck usually finds several unreferenced files
and removes them.  I haven't noticed any important files missing.

Bruce