From: kin loo <kinloo88@gmail.com>
To: 9fans@9fans.net
Subject: Re: [9fans] fossil file system corrupts after a power cut
Date: Wed, 27 Jul 2011 08:39:53 +0000 [thread overview]
Message-ID: <2c9f04ea-3e73-4350-8762-ece5a4b7d133@a2g2000prf.googlegroups.com> (raw)
In-Reply-To: <e79140c4-f440-4659-9684-ca7316e61891@r28g2000prb.googlegroups.com>
On Jul 26, 3:55 pm, 0in...@gmail.com (David du Colombier) wrote:
> > fossil/flfmt -v da39a3ee5e6b4b0d3255bfef95601890afd80709 /dev/sdC0/fossil
> > fatal error: corrupted root: vtRootUnpack
>
> This Venti score is wrong. This is the Venti score returned by an empty
> Fossil file system. That's why it cannot be found in Venti.
>
> > /boot/fossil: cacheLocalData: addr=1 type got 0 exp 8: tag got 0 exp 1
> > /boot/fossil: fsOpen error fsOpen: block label mismatch fsys main
>
> The type VtDataType was returned instead of VtDirType and the tag
> BadTag was returned instead of RootTag. Obviously, something got wrong.
>
> It looks like your virtual hard disk image was corrupted
> because of the the power outage. Especially since you used
> the dynamically-growing qcow2 image format.
>
> You should make another hard disk image and rebuild
> Fossil from your last Venti score.
>
> Since this score cannot be found in your Fossil super block, you
> should extract a list of your Vac scores from your Venti server
> with the script /sys/src/cmd/venti/words/dumpvacroots.
>
> --
> David du Colombier
Thank you David du Colombier, it works. I can now use the most recent
score produced by dumpvacroots to restore the active and archive data
in a new qemu image. But the original 9fat partition still keeps in
the old qcow2 image.
next prev parent reply other threads:[~2011-07-27 8:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-25 16:15 kin loo
2011-07-26 7:53 ` David du Colombier
2011-07-27 8:39 ` kin loo [this message]
2011-07-27 13:48 ` Nicolas Bercher
2011-07-27 14:14 ` Iruatã Souza
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=2c9f04ea-3e73-4350-8762-ece5a4b7d133@a2g2000prf.googlegroups.com \
--to=kinloo88@gmail.com \
--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).