9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] growing/shrinking venti arena files -OR- arena file format
Date: Mon, 26 Nov 2012 08:42:58 -0500	[thread overview]
Message-ID: <fb2c57e5c512c5e85a222a0526d23146@brasstown.quanstro.net> (raw)
In-Reply-To: <86haochpd8.fsf@cmarib.ramside>

> I'm wondering if anyone can shed some light on growing and/or shrinking
> arena files (i.e., disk partitions).  With the growing popularity of
> logical volume management, vitrualization, etc., resizing partitions is
> becoming more and more common, and many file systems already have
> "resize" tools or options to grow/shrink file system structures
> according to changes in the size of the underlying device.  I'm
> wondering what capacities (if any) venti has for dealing with inceases
> or decresases in the size of its arena files.

i'll be honest, i don't understand this statement of the problem.  the
venti abstraction has some answers for this problem.  so i would be disinclined
to look "under the covers" to start.

venti arenas are very small (~650mb) and fill in order.  so taking away empty
arenas should be no problem, while taking away partial arenas will lead
to data loss.  650mb seems like rounding error with today's storage, so
personally i would ignore the problem of resizing an arena.  alternatively,
if one has truely tiny storage, i would be tempted to start with very small
arenas, and still add or remove full arenas.  worst case, i think venti/copy
can be used to recover a deleted last arena to a smaller one.  but the temporary
storage requirements are a bit greater.

- erik



  parent reply	other threads:[~2012-11-26 13:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-26  6:04 smiley
2012-11-26  7:07 ` lucio
2012-11-26 13:42 ` erik quanstrom [this message]
2012-11-26 16:12 Brian L. Stuart

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=fb2c57e5c512c5e85a222a0526d23146@brasstown.quanstro.net \
    --to=quanstro@quanstro.net \
    --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).