From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Corrupted file entry on QEMU - how to recover?
Date: Wed, 19 Dec 2007 21:02:17 -0500 [thread overview]
Message-ID: <fa217a52c2da3cd5f94ffa879b562e12@quanstro.net> (raw)
In-Reply-To: <E6549EBC-C5AE-42DC-A143-111457AC7599@mac.com>
> fsOpen error
> fsOpen: fileRoot: corrupted file entry
>
> No matter how I word open, this error comes up. My question: why not
> just check fix the raw data?
fossil can't open the root and can't help you. i've suggested using
fossil/flchk but you don't want to do that. i think that's as close
to "checking the raw data" as you can get. why don't you want
to use the tool available?
- erik
next prev parent reply other threads:[~2007-12-20 2:02 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-16 2:48 Pietro Gagliardi
2007-12-16 9:10 ` Skip Tavakkolian
2007-12-16 14:22 ` Pietro Gagliardi
2007-12-16 16:25 ` erik quanstrom
2007-12-16 16:54 ` Pietro Gagliardi
2007-12-16 17:25 ` erik quanstrom
2007-12-16 23:57 ` Pietro Gagliardi
2007-12-17 1:34 ` Pietro Gagliardi
2007-12-17 1:36 ` Pietro Gagliardi
2007-12-17 1:42 ` erik quanstrom
2007-12-17 1:57 ` Pietro Gagliardi
2007-12-17 19:24 ` john
2007-12-17 21:10 ` Pietro Gagliardi
2007-12-18 18:13 ` erik quanstrom
2007-12-18 18:19 ` erik quanstrom
2007-12-19 21:02 ` Pietro Gagliardi
2007-12-20 1:15 ` Juan M. Mendez
2007-12-20 1:52 ` Pietro Gagliardi
2007-12-20 2:02 ` erik quanstrom [this message]
2007-12-20 2:10 ` Pietro Gagliardi
2007-12-20 19:58 ` Pietro Gagliardi
2007-12-22 22:29 ` Pietro Gagliardi
2007-12-23 2:35 ` Bakul Shah
2007-12-27 16:23 ` Russ Cox
2007-12-29 16:33 ` Pietro Gagliardi
2007-12-29 19:06 ` Pietro Gagliardi
2008-01-01 1:37 ` Pietro Gagliardi
2008-01-11 20:01 ` Pietro Gagliardi
2008-01-11 20:47 ` Pietro Gagliardi
2008-01-11 22:29 ` Pietro Gagliardi
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=fa217a52c2da3cd5f94ffa879b562e12@quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@cse.psu.edu \
/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).