From: "Brian L. Stuart" <blstuart@bellsouth.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Corrupted meta data
Date: Thu, 17 Jul 2008 15:39:29 +0000 [thread overview]
Message-ID: <071720081539.15506.487F67B100069DA300003C9222230650629B0A02D2089B9A019C04040A0DBF9B9D0E9A9B9C040D@att.net> (raw)
In-Reply-To: <20080716215855.15A9F1E8C1C@holo.morphisms.net>
> 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
next prev parent reply other threads:[~2008-07-17 15:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-16 21:25 Brian L. Stuart
2008-07-16 22:01 ` Russ Cox
2008-07-17 15:39 ` Brian L. Stuart [this message]
2008-07-17 16:20 ` Russ Cox
2008-07-17 17:56 ` Brian L. Stuart
2008-07-17 18:40 ` Brian L. Stuart
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=071720081539.15506.487F67B100069DA300003C9222230650629B0A02D2089B9A019C04040A0DBF9B9D0E9A9B9C040D@att.net \
--to=blstuart@bellsouth.net \
--cc=9fans@9fans.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).