From: gdiaz@online.ie
To: 9fans@cse.psu.edu
Subject: Re: [9fans] venti crashes at startup
Date: Wed, 10 Nov 2004 10:03:01 +0100 [thread overview]
Message-ID: <30a77cf3c1592a5565de802269af2f60@ipsoluciones.com> (raw)
In-Reply-To: <88a47756041106070112f83985@mail.gmail.com>
>
> Does this mean that after I copy a lot of big files to the plan9
> system I have to made a snapshot and then remove the files from fossil
> and use the venti dump archive instead?
>
if you haven't enough space in your fossil yes, but remember, that you cannot re-write files to venti, so the only operation you can do with venti-files is read or write a new one.
I think you shoul make a fossil enough big to work, and venti enough big to store the snaps from that big-fossil.
> I'm not sure if my current fossil/venti setup work as expected because
> I don't get any output from snap -a.
>
snap -a should report vac number, used to generate the cache-fs if needed, (read 9fans archive to obtain more information about vac number and fossil recovery) and remember that snapshots takes a bit of time to complete, so be patient.
if you want to test, use history(1) or yesterday(1) commands, they should work.
gabi
next prev parent reply other threads:[~2004-11-10 9:03 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-03 8:28 Matthias Teege
2004-11-03 8:40 ` C H Forsyth
2004-11-03 8:58 ` Tiit Lankots
2004-11-03 9:35 ` Matthias Teege
[not found] ` <38c3fbecc91da8da2200ca416342ca86@vitanuova.com>
2004-11-03 9:27 ` Matthias Teege
2004-11-03 10:47 ` Heiko Dudzus
2004-11-03 12:30 ` C H Forsyth
2004-11-03 16:01 ` Matthias Teege
2004-11-03 16:41 ` Heiko Dudzus
2004-11-03 17:12 ` gdiaz
2004-11-06 15:01 ` Matthias Teege
2004-11-06 15:15 ` andrey mirtchovski
2004-11-06 17:01 ` Heiko Dudzus
2004-11-10 9:03 ` gdiaz [this message]
2004-11-10 10:36 ` Matthias Teege
2004-11-10 12:42 ` Steve Simon
2004-11-06 15:27 andrey mirtchovski
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=30a77cf3c1592a5565de802269af2f60@ipsoluciones.com \
--to=gdiaz@online.ie \
--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).