From owner-freebsd-current Fri Sep 18 22:21:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA20931 for freebsd-current-outgoing; Fri, 18 Sep 1998 22:21:10 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gatekeeper.tsc.tdk.com (gatekeeper.tsc.tdk.com [207.113.159.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA20926 for ; Fri, 18 Sep 1998 22:21:08 -0700 (PDT) (envelope-from gdonl@tsc.tdk.com) Received: from sunrise.gv.tsc.tdk.com (root@sunrise.gv.tsc.tdk.com [192.168.241.191]) by gatekeeper.tsc.tdk.com (8.8.8/8.8.8) with ESMTP id WAA19458 for ; Fri, 18 Sep 1998 22:20:44 -0700 (PDT) (envelope-from gdonl@tsc.tdk.com) Received: from salsa.gv.tsc.tdk.com (salsa.gv.tsc.tdk.com [192.168.241.194]) by sunrise.gv.tsc.tdk.com (8.8.5/8.8.5) with ESMTP id WAA13626 for ; Fri, 18 Sep 1998 22:20:43 -0700 (PDT) Received: (from gdonl@localhost) by salsa.gv.tsc.tdk.com (8.8.5/8.8.5) id WAA09949 for current@freebsd.org; Fri, 18 Sep 1998 22:20:40 -0700 (PDT) Date: Fri, 18 Sep 1998 22:20:40 -0700 (PDT) From: Don Lewis Message-Id: <199809190520.WAA09949@salsa.gv.tsc.tdk.com> To: current@FreeBSD.ORG Subject: softupdates & fsck Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG While doing various evil things with a machine running current, I've managed to get it to panic a number of times. That and getting some filesystem damage as a result don't bother me, but I am bothered by the type of filesystem damage that I'm seeing. When fsck runs at boot time, it finds a number of orphaned directories, which it reconnects in lost+found. For some reason, they end up with their link count being too low. If I try to "rm -r" them, they are emptied of their contents, except for "." and "..", at which point they are unremovable because their link count is 1 instead of 2. I've also seen directories elsewhere in the tree end up with a link count that's too low. If I unmount the filesystem and run fsck again, fsck notices the problem, reports "UNEXPECTED SOFTDEP INCONSISTENCY", and fixes the problem. There may be files with the wrong link count as well. My suspicion is that the first fsck run is getting the link counts wrong when it repairs the filesystem. I've taked a look at the fsck code, but haven't gotten too far, mostly because the code is so well commented -- NOT! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message