From: erik quanstrom <quanstro@coraid.com>
To: 9fans@9fans.net
Subject: Re: [9fans] when to use vac -q -d old.vac instead of simply vac -dold.vac
Date: Mon, 29 Jun 2009 08:23:03 -0400 [thread overview]
Message-ID: <034f42f5a19e3ebb5934011054ee1ed9@coraid.com> (raw)
In-Reply-To: <20090629050231.GS25893@gradx.cs.jhu.edu>
> On Mon, Jun 29, 2009 at 09:13:09AM +0800, Fernan Bolando wrote:
> > Why is -q not a default? Is there a reliability concern with that option?
>
> It uses an astronomically large amount of memory, if nothing else.
> Mirroring a little over 100MB of data from sources with vac -q occupies
> roughly 85MB in core.
one would think that 20 bytes per file + fixed buffer would be enough.
- erik
next prev parent reply other threads:[~2009-06-29 12:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-29 1:13 [9fans] when to use vac -q -d old.vac instead of simply vac -d old.vac Fernan Bolando
2009-06-29 5:02 ` Nathaniel W Filardo
2009-06-29 12:23 ` erik quanstrom [this message]
2009-06-29 15:56 ` Russ Cox
2009-07-02 1:54 ` Nathaniel W Filardo
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=034f42f5a19e3ebb5934011054ee1ed9@coraid.com \
--to=quanstro@coraid.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).