From owner-freebsd-questions@FreeBSD.ORG Thu Jan 20 20:01:10 2005 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CBF3516A4CE for ; Thu, 20 Jan 2005 20:01:10 +0000 (GMT) Received: from mail.meangrape.com (mail.meangrape.com [209.223.7.159]) by mx1.FreeBSD.org (Postfix) with SMTP id 544D643D2F for ; Thu, 20 Jan 2005 20:01:10 +0000 (GMT) (envelope-from jay@meangrape.com) Received: (qmail 71173 invoked by uid 1002); 20 Jan 2005 20:04:04 -0000 Date: Thu, 20 Jan 2005 14:04:04 -0600 From: Jay To: freebsd-questions@freebsd.org Message-ID: <20050120200404.GC60107@mail.meangrape.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.6i Subject: snapshots, soft update inconsistency X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Jan 2005 20:01:10 -0000 I've got some filesystem problems on my /usr partition. Cause: power failures caused by TWO exploding transformers I restarted in single-user mode and fsck'd all of my partitions. Everything looked fine. I've got a handful of zero-length files that I can't fix. "Bad file descriptor". I've tried `ls -i` to get the inode number so I can delete the files via find. ls doesn't work -- it just returns "Bad file descriptor". I then had the bright idea of making a snapshot and running fsck against it. I got a few hundred lines of "unexpected soft update inconsistency". I didn't have fsck repair anything against the snapshot; I just wanted to see what the output was. Should I: a) run fsck against the snapshot and let it fix things b) go back to single-user mode and run fsck c) do something else I'm sure that booting into single-user mode is the best idea, however, I'd prefer not to do that if possible -- the machine is up and running and doing it's thing fairly well at the moment. I still have the undeleteable zero-length file problem, and any suggestions would be appreciated. I think it's probably wise to handle the larger problem first. Thanks. -- Jay.