9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Russ Cox" <rsc@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: [9fans] venti
Date: Fri, 29 Nov 2002 13:27:21 -0500	[thread overview]
Message-ID: <359cc15e935bacf9289f0d28300a21f7@plan9.bell-labs.com> (raw)

[A side note:

A number of people have reported not being able to connect
to sources.cs.bell-labs.com.  Our external DNS seems to be
very slow.  I'm not sure exactly what's wrong, but until we
fix it you can use:

	echo 'dom=sources.cs.bell-labs.com sys=sources ip=204.178.31.8' >>/net/ndb
	echo -n refresh >/net/cs

as a workaround.]

There's a new command venti/wrarena, which complements rdarena.
 From ventiaux(8):

          venti/wrarena [ -o fileoffset ] [ -h host ] arenafile [
          clumpoffset ]

          Wrarena writes the blocks contained in the arena arenafile
          (typically, the output of rdarena) to a Venti server.  It is
          typically used to reinitialize a Venti server from backups
          of the arenas.  For example,

               venti/rdarena /dev/sdC0/arenas arena.0 >external.media
               venti/wrarena -h venti2 external.media

          writes the blocks contained in arena.0 to the Venti server
          venti2 (typically not the one using /dev/sdC0/arenas).

          The -o option specifies that the arena starts at byte
          fileoffset (default 0) in arenafile . This is useful for
          reading directly from the Venti arena partition:

               venti/wrarena -h venti2 -o 335872 /dev/sdC0/arenas

          (In this example, 335872 is the offset shown in the Venti
          server's index list (344064) minus one block (8192).  You
          will need to substitute your own arena offsets and block
          size.)

          Finally, the optional offset argument specifies that the
          writing should begin with the clump starting at offset
          within the arena.  Wrarena prints the offset it stopped at
          (because there were no more data blocks).  This could be
          used to incrementally back up a Venti server to another
          Venti server:

               last=`{cat last}
               venti/wrarena -h venti2 -o 335872 /dev/sdC0/arenas $last >output
               awk '/^end offset/ { print $3 }' output >last

          (Of course, one would need to add wrapper code to keep track
          of which arenas have been processed.)

Russ


             reply	other threads:[~2002-11-29 18:27 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-29 18:27 Russ Cox [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-01-09  8:20 Tharaneedharan Vilwanathan
2009-01-09  9:44 ` Sape Mullender
2009-01-09 12:18   ` Richard Miller
2009-01-09 12:38     ` Sape Mullender
2009-01-09 13:39     ` erik quanstrom
2009-01-09 20:11   ` Dave Eckhardt
2009-01-09 20:27     ` erik quanstrom
2009-01-09 22:18       ` Dave Eckhardt
2009-01-09 22:27         ` erik quanstrom
2009-01-09 20:34     ` Steve Simon
2009-01-09 21:08     ` Roman V. Shaposhnik
2007-10-04  1:51 Russ Cox
2007-10-07 20:51 ` Steve Simon
2007-07-03  4:58 [9fans] Venti Lucio De Re
2007-03-30 16:32 [9fans] venti Steve Simon
2003-02-06  1:11 Kenji Arisawa
2003-02-06  1:21 ` Russ Cox
2002-11-29 18:59 Russ Cox
2002-06-13 20:58 [9fans] bug or a feature? Dan Cross
2002-06-13 21:34 ` Tharaneedharan Vilwanathan
2002-06-13 22:51   ` [9fans] venti Tharaneedharan Vilwanathan
2002-06-14  2:19     ` Sean Quinlan
2002-06-14  5:05       ` Tharaneedharan Vilwanathan
2002-01-30 20:35 George Michaelson
     [not found] <rob@plan9.bell-labs.com>
2002-01-30  5:52 ` rob pike
2002-01-30  6:23   ` George Michaelson
2002-01-30  8:07   ` paurea
2002-01-30 11:17   ` Boyd Roberts

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=359cc15e935bacf9289f0d28300a21f7@plan9.bell-labs.com \
    --to=rsc@plan9.bell-labs.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).