From mboxrd@z Thu Jan  1 00:00:00 1970
From: "Brian L. Stuart" <blstuart@bellsouth.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Date: Thu, 17 Jul 2008 15:39:29 +0000
Message-Id: <071720081539.15506.487F67B100069DA300003C9222230650629B0A02D2089B9A019C04040A0DBF9B9D0E9A9B9C040D@att.net>
In-Reply-To: <20080716215855.15A9F1E8C1C@holo.morphisms.net>
References: <071620082125.14638.487E6732000757100000392E22230703729B0A02D2089B9A019C04040A0DBF9B9D0E9A9B9C040D@att.net>
	<20080716215855.15A9F1E8C1C@holo.morphisms.net>
Subject: Re: [9fans] Corrupted meta data
Topicbox-Message-UUID: eabd55f8-ead3-11e9-9d60-3106f5b1d025

> Can you clri the file from fossilcons?

Unfortunately, that just reports the corrupted meta data too.
Interestingly, when I started it up this morning, the check
didn't report an error with it.  But then after trying to
access it, check now reports:
error: could not unpack meta block: /active/sys/src/9/pc[3]: corrupted meta data
What does the 3 refer to?  The 3rd block of the pc directory,
maybe?

The pc directory itself seems fine.  I can see everything
else there.  main.8 doesn't show up in an lc.  If my current
directory is elsewhere and I try to ls -l /n/fossil/sys/src/9/pc/main.8,
it comes up as not existing.  But if my current directory
is /n/fossil/sys/src/9/pc, then I get the corrupted meta
data error.

I haven't changed anything in that directory, so in principle,
I guess i could blow away the directory (clri if necessary)
and copy it all back from a venti snapshot.  But before I
do that, I'd like to see if a more direct recovery is possible.

BTW, I had it lock up again this morning.  I've noticed that
when it does, it uses 100% of the CPU.  It's acting like
it's stuck in a spin lock.  I can't say for sure, so this
may be a red herring, but it has seemed that every time
it's locked up, it's been when doing I/O to the sdloop
device.

Thanks,
BLS