9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Gregory Pavelcak" <pavelcak@gmail.com>
To: 9fans@9fans.net
Subject: [9fans] Subject: Venti, redundancy, and hardware failure.
Date: Sat,  2 Aug 2008 09:59:08 -0400	[thread overview]
Message-ID: <6256dcf20808020659r18a22e6iedc08662f89e74c2@mail.gmail.com> (raw)

Sorry if this is a repost, but I haven't seen it show up on groups, so
I think I'm OK.

I recently asked about mirroring venti arenas and was told that mirroring
is generally a good idea.  It
occurred to me that, although I know how to mirror my arenas, I'm not
clear on how to recover from hardware failure.  That is, suppose sdD0
and sdD1 are dedicated to arenas, they are mirrored, and venti.conf
has something like 'arenas /dev/fs/arenas'.  Now suppose sdD0 goes
belly up.  Do I change '/dev/fs/arenas' to '/dev/sdD1/arenas', in
venti.conf and fossil conf?  Maybe rerun fmtindex?  I recall reading
about setting up venti and recovering fossil from venti, but I don't
remember seeing anything about this.

Also, I was looking at venti-backup.  I assume that using it to
'incrementally back up a Venti server to another Venti server' could
also include just copying the arenas to another device on the same
machine.  Is that right?  Even if I can use venti-backup tools in this
way, is mirroring preferable when it's possible?  Why or why not?

(Hah!  Sounds like a quiz.  Bad college flashback.  :-))

Greg



             reply	other threads:[~2008-08-02 13:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-02 13:59 Gregory Pavelcak [this message]
2008-08-03 15:49 ` Russ Cox
2008-08-03 21:14   ` Steve Simon

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=6256dcf20808020659r18a22e6iedc08662f89e74c2@mail.gmail.com \
    --to=pavelcak@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).