From owner-freebsd-hackers Thu Jan 26 10:49:36 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id KAA00829 for hackers-outgoing; Thu, 26 Jan 1995 10:49:36 -0800 Received: from zibbi.mikom.csir.co.za (zibbi.mikom.csir.co.za [146.64.24.58]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id KAA00819 for ; Thu, 26 Jan 1995 10:49:22 -0800 Received: (from jhay@localhost) by zibbi.mikom.csir.co.za (8.6.9/8.6.6) id PAA06693; Thu, 26 Jan 1995 15:47:12 +0200 From: John Hay Message-Id: <199501261347.PAA06693@zibbi.mikom.csir.co.za> Subject: Re: Directory entries get corrupted? To: peter@bonkers.taronga.com (Peter da Silva) Date: Thu, 26 Jan 1995 15:47:12 +0200 (SAT) Cc: hackers@FreeBSD.org In-Reply-To: <199501261237.GAA07421@bonkers.taronga.com> from "Peter da Silva" at Jan 26, 95 06:37:29 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 588 Sender: hackers-owner@FreeBSD.org Precedence: bulk > > Anything fsck tells you about an active file system should be taken with > a pinch of salt, a spoonful of sugar, and extreme suspicion. After all, it's > setpping through the disk looking for pointers to the wrong places while the > O/S is moving those pointers out from under it. It's no surprise that some > times the pointy end of a pointer is pointing to a block that's actually > holding something that pointer shouldn't be pointing to by the time it gets > around to it. > I get the same errors if I unmount that disk before doing the fsck. John Hay -- jhay@mikom.csir.co.za