From: "Devon H. O'Dell" <devon.odell@gmail.com>
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 11:29:58 -0400 [thread overview]
Message-ID: <9ab217670703230829k26314acakf77d8e26fd415e14@mail.gmail.com> (raw)
In-Reply-To: <17126495d2ff27dd7886029e979f050f@hamnavoe.com>
2007/3/23, Richard Miller <9fans@hamnavoe.com>:
> Devon -
>
> > This morning I'm still at 14GB. I mean, I should note that I'm not
> > actually removing any files or anything, and I still have the 25GB of
> > MP3s that were on there at the beginning. So. Still confused and
> > frustrated.
>
> Why are you expecting your fossil partition to become more empty?
> It's a cache - so even when a block has been copied to venti, it
> is still useful to keep a copy in fossil as well, in case it's referenced
> again. It will be marked 'clean', so that it can be evicted from the
> cache instantly if fossil runs out of space.
>
> Are you still worried that blocks aren't being copied to venti at all?
> You can check by looking at the archive score which is printed
> on fossilcons right after a 'snap -a' is done. You can use vacfs
> to mount this score as a fs, and then explore that to see if everything
> is there.
I'm not sure what you're referring to here -- when I type snap -a, I
get no output back.
> If you *really* want to empty your fossil partition, you can reformat
> it immediately after a 'snap -a', using the '-v score' option with the
> score of the snap you just made. (Take the usual precautions first,,
> of course.)
I'll read the fossilcons manpage on this again and see what the usage
of this is. I guess I am somewhat worried, simply because I don't want
to fill my fossil partition (I still have > 35GB data to copy over)
and have it blow up.
At this point, I think I've probably munged what's in Venti enough
that I'm going to go ahead and reinstall with this `newfound'
knowledge.
> -- Richard
Thanks for the information -- I'll definitely try it out this time.
--dho
next prev parent reply other threads:[~2007-03-23 15:29 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
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 [this message]
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=9ab217670703230829k26314acakf77d8e26fd415e14@mail.gmail.com \
--to=devon.odell@gmail.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).