From: Lyndon Nerenberg <lyndon@orthanc.ca>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] file server?
Date: Fri, 14 Aug 2009 00:14:29 -0600 [thread overview]
Message-ID: <alpine.BSF.2.00.0908140000060.8707@legolas.yyc.orthanc.ca> (raw)
In-Reply-To: <7d3530220908131823u1d5e3b9bk22632a1cce07f38b@mail.gmail.com>
> This is what we do at Sandia. We have one machine which serves
> cpu/auth/file, but the actual Venti disks are in a Coraid connected
> via GigE. The fossil disk is in the server, but if it dies we can just
> build a new one.
Which reminds me of an often overlooked but important point:
Save your fossil vac scores on another machine!
Without them, your seperate venti server is JBOD :-P Well, not quite. You
can eventually find the right vac score, but you have to manually mount
each and every score in the venti until you find the right one. See
/sys/src/cmd/venti/words/dumpvacroots. You could probably semi-automate
the process by writing a script that mounted each of the scores in turn,
checking the mtime of something like /sys/log/timesync in each, and
sorting the vac scores accordingly.
On my setup I aux/clog the fileserver console to a u9fs mounted directory
on a UNIX server. You could also cobble something up that scans the fossil
console for vac scores and emails them to an offsite address.
--lyndon
next prev parent reply other threads:[~2009-08-14 6:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-14 0:30 Benjamin Huntsman
2009-08-14 0:55 ` andrey mirtchovski
2009-08-14 1:01 ` erik quanstrom
2009-08-14 1:23 ` John Floren
2009-08-14 2:00 ` erik quanstrom
2009-08-14 6:14 ` Lyndon Nerenberg [this message]
2009-08-14 8:45 ` Robert Raschke
2009-08-14 12:07 ` erik quanstrom
2009-08-14 12:44 ` Robert Raschke
2009-08-14 12:09 ` erik quanstrom
2009-08-16 2:12 ` Adrian Tritschler
2009-08-14 4:16 ` Lyndon Nerenberg
2009-08-14 1:09 ` Federico G. Benavento
2009-08-14 1:15 ` blstuart
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=alpine.BSF.2.00.0908140000060.8707@legolas.yyc.orthanc.ca \
--to=lyndon@orthanc.ca \
--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).