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: Sat, 29 Dec 2007 14:06:23 -0500 [thread overview]
Message-ID: <B3E09280-85EC-4E23-BD5F-3F285B7C594B@mac.com> (raw)
In-Reply-To: <4584997B-ED8E-4B07-99DC-3E14CB93D909@mac.com>
Right now, I'm trying to get function definitions off of the plan9
file so I can rebuild my profile. This should be as easy as grep.
On Dec 29, 2007, at 11:33 AM, Pietro Gagliardi wrote:
> OK, I'm going to hold this off for the new year. Until then, I
> managed to free up a lot of space (and am continuing to do so), so
> this time I'll put up a new 4GB QEMU fossil+venti Plan 9 and save
> the old disk until I can fix it.
>
> On Dec 27, 2007, at 11:23 AM, Russ Cox wrote:
>
>>> Can someone PLEASE give me some information so I can get my files
>>> back? Otherwise, there goes my 3D library, my hoc implementation,
>>> etc.
>>
>> I'm afraid you're probably out of luck, without a lot of work.
>>
>> The disk data structures are all described in /sys/doc/fossil.ps.
>>
>> If you were using snapshots, then you might be able to
>> use the information in /sys/doc/fossil.ps to write a program
>> to find all the fossil snapshot roots, and then you
>> could rewrite the super block to point at an older,
>> hopefully not corrupt, root.
>>
>> However, it looks like in plain fossil mode (not fossil+venti),
>> the installer does not configure any snapshots, so you'd
>> have had to turn them on yourself.
>>
>> Without snapshots, you'd have to poke around on the
>> disk looking for a VtSource that looked like the root
>> directory and then fix up the root block to be valid and
>> point at it.
>>
>> If you're not used to poking at file system data structures,
>> this might well be more work than just recreating your
>> hoc and 3D code.
>>
>> Russ
>>
>
next prev parent reply other threads:[~2007-12-29 19:06 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
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 [this message]
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=B3E09280-85EC-4E23-BD5F-3F285B7C594B@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).