From owner-freebsd-current Tue Jul 23 15:09:03 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA18622 for current-outgoing; Tue, 23 Jul 1996 15:09:03 -0700 (PDT) Received: from freefall.freebsd.org (localhost.cdrom.com [127.0.0.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id PAA18615; Tue, 23 Jul 1996 15:09:01 -0700 (PDT) Message-Id: <199607232209.PAA18615@freefall.freebsd.org> To: sos@FreeBSD.org cc: julian@freefall.freebsd.org (Julian Elischer), current@freefall.freebsd.org, hackers@freefall.freebsd.org Subject: Re: anyone have a clue on this bug? In-reply-to: Your message of "Tue, 23 Jul 1996 23:30:50 +0200." <199607232130.XAA00352@DeepCore.dk> Date: Tue, 23 Jul 1996 15:09:01 -0700 From: "Justin T. Gibbs" Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk >In reply to Julian Elischer who wrote: >> >> It's bitten us several times on recent -current machines.. >> >> due to some problem, a system dies.. >> (bad h/w or whatever..) >> on reboot it is discovered that some the files that were open at >> the time of the reboot have been deleted by fsck >> (i.e. they had 0 references or something) >> >> it's particulary annoying when it deletes the console or some other >> useful device.. I've mainly seen it with devices, >> but I think I have also seen directories mutating into devices >> and files doing other odd things.. > >Seems like bad hw, I havn't seen anything like this, except when I >tried out DEVFS long ago.... I've seen fsck eat things I didn't think it should have before. I never looked into fsck itself though, I just fixed the bugs in my driver that would cause hangs. 8-( >-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- >Søren Schmidt (sos@FreeBSD.org) FreeBSD Core Team > Even more code to hack -- will it ever end >.. -- Justin T. Gibbs =========================================== FreeBSD: Turning PCs into workstations ===========================================