From: Russ Cox <rsc@swtch.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] when to use vac -q -d old.vac instead of simply vac -d old.vac
Date: Mon, 29 Jun 2009 08:56:06 -0700 [thread overview]
Message-ID: <dd6fe68a0906290856q3aacb3a8g86bd76ca4063114e@mail.gmail.com> (raw)
In-Reply-To: <1d5d51400906281813g649a72f7v8610b0311c7de5f@mail.gmail.com>
On Sun, Jun 28, 2009 at 6:13 PM, Fernan Bolando<fernanbolando@mailc.net> wrote:
> man vac
> "-q Increase the performance of the -a or -d options by detecting
> unchanged files based on a
> match of the files name and other meta data, rather than
> examining the contents of the files"
>
> Why is -q not a default? Is there a reliability concern with that option?
If the file contents change but the mtime and size remain
the same, then vac -q will not notice the change and will
not back up the new file contents. Some people worry
about this case, others don't. Hence the flag.
> I am currently doing an hourly backup using
>
> vac -d old_date-time.vac -f new_date-time.vac /home
> which gives me a collection files with a date-time.vac filename.
>
> I am thinking I should just use vac -a main.vac /home
> to switch to this method I only need to rename latest date-time.vac to main.vac
> and delete the other ones, right?
vac -a creates a tree inside the vac archive.
It expects the archive to have a top-level
directory 2009 and subdirectories 0627, 0628, etc.
You would need to change your vac tree to have
that top-level structure before it would be
valid input to vac -a. If you run it multiple
times per day, the subdirectories for today
would be named 0629, 0629.1, 0629.2, 0629.3,
and so on. You can do this by building a
local file tree with the right structure and using
vac -m.
On Sun, Jun 28, 2009 at 10:02 PM, Nathaniel W Filardo<nwf@cs.jhu.edu> wrote:
> 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.
Whether you use -q should have no effect on the memory usage.
There may be a memory leak somewhere involving -q, but at
first glance I don't see one. Feel free to investigate.
Russ
next prev parent reply other threads:[~2009-06-29 15:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-29 1:13 Fernan Bolando
2009-06-29 5:02 ` Nathaniel W Filardo
2009-06-29 12:23 ` [9fans] when to use vac -q -d old.vac instead of simply vac -dold.vac erik quanstrom
2009-06-29 15:56 ` Russ Cox [this message]
2009-07-02 1:54 ` [9fans] when to use vac -q -d old.vac instead of simply vac -d old.vac 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=dd6fe68a0906290856q3aacb3a8g86bd76ca4063114e@mail.gmail.com \
--to=rsc@swtch.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).