Date: Thu, 20 Jan 2005 14:04:04 -0600 From: Jay <jay@meangrape.com> To: freebsd-questions@freebsd.org Subject: snapshots, soft update inconsistency Message-ID: <20050120200404.GC60107@mail.meangrape.com>
next in thread | raw e-mail | index | archive | help
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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050120200404.GC60107>