9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Pietro Gagliardi <pietro10@mac.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] Corrupted file entry on QEMU - how to recover?
Date: Wed, 19 Dec 2007 20:52:06 -0500	[thread overview]
Message-ID: <E6549EBC-C5AE-42DC-A143-111457AC7599@mac.com> (raw)
In-Reply-To: <acb195480712191715p35710401u5d23701d44b53e0b@mail.gmail.com>

I'm sorry, I still get the errors. I'll print them verbatim:

	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?

PS - The -V option to open can be used to avoid venti checking.

On Dec 19, 2007, at 8:15 PM, Juan M. Mendez wrote:

> On 19/12/2007, Pietro Gagliardi <pietro10@mac.com> wrote:
>> I'd still like to know how to check my file system without dealing
>> with fsOpen, if that is possible. Does anyone know how?
>
>
> I posted this in another topic, maybe it gives you ideas of how to
> deal with your problem.
> Whenever I have problems with my disk (a real old bad disk) I do  
> this to get my
> fossil only file system fixed:
>
> <<
> I booted with the plan9 livecd and did a check to the disk with this.
>
> fossil/fossil -c 'srv -p fscons'
> con /srv/fscons
> prompt: srv -AWP replica
> prompt: fsys main config /dev/sdC0/fossil
> prompt: fsys main open -AWP
> warning: connecting to venti: cs: can't translate address: '/srv/ 
> dns' file
> does not exist
> prompt: fsys main
> main: check fix
>
>>>
> -- 
> Fidonet: 2:345/432.2


  reply	other threads:[~2007-12-20  1:52 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 [this message]
2007-12-20  2:02                       ` erik quanstrom
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=E6549EBC-C5AE-42DC-A143-111457AC7599@mac.com \
    --to=pietro10@mac.com \
    --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).