From: Martin Neubauer <m.ne@gmx.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] Update on Fossil+Venti Stuff
Date: Fri, 23 Mar 2007 07:54:18 +0100 [thread overview]
Message-ID: <20070323065418.GC19118@shodan.homeunix.net> (raw)
In-Reply-To: <9ab217670703222327r7fa24d9bydd174bb7b2e5af55@mail.gmail.com>
* Devon H. O'Dell (devon.odell@gmail.com) wrote:
> 2007/3/23, Martin Neubauer <m.ne@gmx.net>:
> >* Devon H. O'Dell (devon.odell@gmail.com) wrote:
> >> 10.0.0.10# con -l /srv/fscons
> >> prompt: fsys main snaptime
> >> snaptime -a 0500 -s 60 -t 2880
> >>
> >> I should note that I've manually modified this to happen a few times a
> >> day. Each time, my usage goes down a couple gigs. Why doesn't it just
> >> go ahead and sync everything?
> >
> >It does sync everything active. There are probably still some intermediate
> >snapshots there that are not written to venti. Those stay there until they
> >expire after 2 days (2880 minutes). You can always do an explicit snapclean
> >or try lowering the time snapshots are kept.
>
> I'm not disagreeing that this is supposed to happen, and I hate saying
> it's wrong, but it's not what I'm seeing, and I don't see anything
> invalid in my configuration. I can snap -a, and it won't go to venti.
> I ran snapclean and nothing went down. After that, I changed the
> snaptime so that it would run a Venti dump in 5 minutes. 10 minutes
> later, I see no difference.
For snaptime, -a means ``time when to take archival dump.'' So you probably
just made fossil dump 5 minutes after midnight. -s sets the interval (in
minutes) between intermediate snapshots, -t the time (in minutes) after
which old snapshots are discarded. If a snapshot of a file is referenced as
the current version but isn't yet written to venti it is kept until the next
dump.
>
> So I'm either missing something fundamental here, something's really
> broken, or I'm just dumb. I'm willing to concede the latter of the 3,
> but it would be really nice to be enlightened. Is there anything I can
> show you guys to help diagnose the issue further?
If it helps, it took some time for me to get a grasp of the workings, too.
(And I'm sure there are still plenty of pitfalls for me to run into...)
Martin
next prev parent reply other threads:[~2007-03-23 6:54 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-21 20:17 Devon H. O'Dell
2007-03-21 21:02 ` Martin Neubauer
2007-03-21 21:05 ` erik quanstrom
2007-03-21 21:24 ` Bakul Shah
2007-03-22 10:04 ` Richard Miller
2007-03-23 5:17 ` Devon H. O'Dell
2007-03-23 6:14 ` Martin Neubauer
2007-03-23 6:27 ` Devon H. O'Dell
2007-03-23 6:54 ` Martin Neubauer [this message]
2007-03-23 14:24 ` David Leimbach
2007-03-23 15:04 ` Devon H. O'Dell
2007-03-23 15:10 ` Richard Miller
2007-03-23 15:29 ` Devon H. O'Dell
2007-03-23 15:39 ` Richard Miller
2007-03-23 15:47 ` Devon H. O'Dell
2007-03-23 19:23 ` Steve Simon
2007-03-23 15:47 ` Richard Miller
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=20070323065418.GC19118@shodan.homeunix.net \
--to=m.ne@gmx.net \
--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).