From: "Steve Simon" <steve@quintile.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Fossil on devfs
Date: Thu, 2 Feb 2006 23:20:21 +0000 [thread overview]
Message-ID: <84bc479484fefcf7237d8be7525a00ea@quintile.net> (raw)
In-Reply-To: <dac0a5820602021251p2d0d0287i33c38d149dc5bb05@mail.gmail.com>
RE: disk mirroring
Have you cloned the data from your existing fossil to its new mirror,
you must do this by hand (with dd) before you first enable mirroring;
I do this booted from the CDROM.
You should be able to see the mirrored partition and the file containing
fs's config in #k/fs, On my home server:
cpu% ls '#k/fs'
'#k/fs/arenas0'
'#k/fs/ctl'
cpu% cat '#k/fs/ctl'
mirror arenas0 /dev/sd06/arenas0 /dev/sd010/arenas0
cpu%
I use a mirrored venti rather than mirrored fossil but the principal
is the same.
Posting the contents of your plan9.ini, the contents of your fscfg
partition, and the fossil config might help me or others debug the problem,
however if you are using Andreys recpie it should Just Work™
Also rembember, if you are checking for the existance of devfs in your kernel,
if you are connected from a remote plan9/drawterm it may have mounted its
/dev/drivers before your file servers one, try:
cat /dev/dri?ers | grep devfs
-Steve
next prev parent reply other threads:[~2006-02-02 23:20 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-22 19:27 Heiko Dudzus
2005-11-22 19:37 ` Christoph Lohmann
2005-11-22 20:23 ` Russ Cox
2005-11-22 19:37 ` andrey mirtchovski
2005-11-26 13:30 ` Heiko Dudzus
2005-11-26 13:55 ` andrey mirtchovski
2005-11-26 14:34 ` Christoph Lohmann
2005-11-26 14:42 ` andrey mirtchovski
2005-11-26 17:55 ` Heiko Dudzus
2005-11-27 0:54 ` Russ Cox
2005-11-27 0:55 ` Russ Cox
2006-02-02 20:51 ` Tharaneedharan Vilwanathan
2006-02-02 23:20 ` Steve Simon [this message]
2006-02-03 0:18 ` Micah Stetson
2006-02-03 9:10 ` Tharaneedharan Vilwanathan
2006-02-03 18:21 ` Heiko Dudzus
2006-02-04 15:28 ` Tharaneedharan Vilwanathan
2006-02-04 12: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=84bc479484fefcf7237d8be7525a00ea@quintile.net \
--to=steve@quintile.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).