9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: smiley@icebubble.org
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] sealed arena modified by venti??
Date: Thu, 22 Mar 2012 15:34:47 +0000	[thread overview]
Message-ID: <86limstzs8.fsf@cmarib.ramside> (raw)
In-Reply-To: <CADSkJJVtuvZ62twoy=5Gbu3Ur8D83AdVU9_Uucm57hFLhTGxqg@mail.gmail.com> (Russ Cox's message of "Tue, 28 Feb 2012 13:20:25 -0500")

Russ Cox <rsc@swtch.com> writes:

> Try running verifyarena on both.

LOL.  There's a "verifyarena" command?  Silly me, I just had to
s/checkarenas/verifyarena/!

How do you guys know all these obscure command names (let alone what
they do)?  Let me guess... you wrote them?  Plan 9 is really looking
like a hacker's OS... for hackers, by hackers (of hacks??).

(fast forward)

Using some device mapper "magic", I was able to make the backed-up arena
appear at the correct location in the arena file.  The backed-up copy of
the arena verifies OK.  The live copy of the arena is reported to have
an incorrect sum... but that's all it says.

Is there a way to look into an arena a little deeper, to find the
offending data?  I'd like to debug this, and try to find the cause of
this corruption, in order to avoid it in the future.

--
+---------------------------------------------------------------+
|Smiley       <smiley@icebubble.org>    PGP key ID:    BC549F8B |
|Fingerprint: 9329 DB4A 30F5 6EDA D2BA  3489 DAB7 555A BC54 9F8B|
+---------------------------------------------------------------+



      reply	other threads:[~2012-03-22 15:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-28 18:13 smiley
2012-02-28 18:20 ` Russ Cox
2012-03-22 15:34   ` smiley [this message]

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=86limstzs8.fsf@cmarib.ramside \
    --to=smiley@icebubble.org \
    --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).