From: David du Colombier <0intro@gmail.com>
To: 9fans@9fans.net
Subject: Re: [9fans] Fossil fs recovery
Date: Thu, 11 Aug 2011 10:11:27 +0200 [thread overview]
Message-ID: <20110811101127.52627669@wks-ddc.exosec.local> (raw)
In-Reply-To: <CAP6exYL+Tf6a_8d3NnVYVbrGH3N8JwBwVcMsyS0Zybx_Coaz7A@mail.gmail.com>
In fact, it's pretty straightforward.
In the following example, I consider you have a disk sdE0
with Fossil, and you want to add a disk sdE1 with Venti.
Create the Venti partitions:
disk/fdisk -baw /dev/sdE1/data
disk/prep -bw -a^(isect arenas bloom) /dev/sdE1/plan9
Format the Venti file systems:
venti/fmtisect isect /dev/sdE1/isect
venti/fmtarenas arenas /dev/sdE1/arenas
venti/fmtbloom /dev/sdE1/bloom
Since the bloom filter requires memory equal to its size
on disk, you could need to pass the parameter -s to fmtbloom
to specify its size or directly adjust the partition size.
Keep in mind that Venti use 20% total memory by default, and
1/3 of it is allocated to the bloom filter.
For example, with 1 GB of memory, you cannot have a bloom filter
larger than 64 MB (which is sufficient) with the default settings.
Of course, the bloom filter is optional anyway.
Configure Venti:
echo 'index main
isect /dev/sdE1/isect
arenas /dev/sdE1/arenas
bloom /dev/sdE1/bloom' | venti/conf -w /dev/sdE1/arenas
Initialize the index sections:
venti/fmtindex /dev/sdE1/arenas
Read your current Fossil configuration:
fossil/conf /dev/sdE0/fossil > fossil.conf
Edit fossil.conf, it should look like something like:
fsys main config /dev/sdE0/fossil
fsys main open -V -c 3000
Remove -V to open and srv if needed, then
add the following line to enable automatic
snapshots:
fsys main snaptime -s 60 -a 0530 -t 2880
(snapshot at 05:30, temporary snapshot each
hour and discarded after two days)
Write your new Fossil configuration:
fossil/conf -w /dev/sdE0/fossil < fossil.conf
Mount your 9fat file system, then add the following line
to the file /n/9fat/plan9.ini:
venti=#S/sdE1/arenas
After rebooting, the current Fossil content will be dumped
to Venti.
--
David du Colombier
next prev parent reply other threads:[~2011-08-11 8:11 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-10 16:21 Bernd Maier
2011-08-10 17:46 ` David du Colombier
2011-08-10 21:58 ` Steve Simon
2011-08-10 22:12 ` ron minnich
2011-08-11 8:11 ` David du Colombier [this message]
2011-08-11 13:46 ` David Leimbach
2011-08-11 13:56 ` Jack Norton
2011-08-11 15:37 ` David du Colombier
2011-08-11 15:15 ` Steve Simon
2011-08-11 15:30 ` David du Colombier
2011-08-13 19:12 ` geoff
2011-08-13 23:44 ` Lyndon Nerenberg (VE6BBM/VE7TFX)
2011-08-14 6:21 ` Steve Simon
2011-08-14 11:48 ` Francisco J Ballesteros
2011-08-14 17:55 ` David du Colombier
-- strict thread matches above, loose matches on Subject: below --
2011-08-14 14:49 Bernd Maier
2011-08-12 9:53 Bernd Maier
2011-08-12 12:03 ` David du Colombier
2011-08-10 12:35 Bernd Maier
2011-08-10 15:25 ` Steve Simon
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=20110811101127.52627669@wks-ddc.exosec.local \
--to=0intro@gmail.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).