9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: ron minnich <rminnich@lanl.gov>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] vacfs
Date: Fri,  6 Feb 2004 21:21:25 -0700	[thread overview]
Message-ID: <Pine.LNX.4.44.0402062113510.18991-100000@maxroach.lanl.gov> (raw)
In-Reply-To: <Pine.LNX.4.44.0402061942560.18350-100000@maxroach.lanl.gov>

OK, vacfs is working fine on the node with the dead fossil and the still
valid venti arenas.

Here is what is neat: I had 2 arenas and 2 indexes, which I laid out this
way by following the wiki and man pages. The CDROM venti was very unhappy
with the 2 indexes, so I took a chance, changed the config file to only
have one index (/dev/sdC0/isect0), and rebuilt the index with buildindex.

All this from the CD. All the source available for perusal, so confusion
could be reduced. Any time things got weird, slay venti and start over.

Then I sucked the good score from the dead fossil, and using that score I
have been able to use vacfs to get my last venti mounted via vacfs.

Venti is very impressive, and these tools are really pretty slick.

Looks like I can recover my files, which is a real relief.

One thing that will always be useful is the FAT partition. It's just a
handy place to have around in the event of disaster and you have to boot
from CD. I think I'm going to make it bigger in future just to have it
there. Sure you have ramfs but if you have to reboot you don't want to
lose any temp files you've worked up.

ron



  parent reply	other threads:[~2004-02-07  4:21 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-07  2:37 ron minnich
2004-02-07  2:43 ` ron minnich
2004-02-07  2:57   ` ron minnich
2004-02-07  3:04     ` boyd, rounin
2004-02-09 17:13     ` rog
2004-02-07  4:21   ` ron minnich [this message]
2004-02-07  4:35     ` boyd, rounin
2004-02-08  2:41       ` Joel Salomon
2004-02-08 16:32         ` ron minnich
2004-02-08 17:29           ` Charles Forsyth
2004-02-08 22:03             ` Wes Kussmaul
2004-02-08 17:30           ` a
2004-02-07  5:38 ` vdharani

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=Pine.LNX.4.44.0402062113510.18991-100000@maxroach.lanl.gov \
    --to=rminnich@lanl.gov \
    --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).