From: "Steve Simon" <steve@quintile.net>
To: 9fans@9fans.net
Subject: [9fans] devfs mirroring
Date: Fri, 2 Dec 2011 12:17:42 +0000 [thread overview]
Message-ID: <bb909f5842577098a187a158bbe18c12@quintile.net> (raw)
I have a mirrored pair of disks under devfs.
I have a series of 512 byte partitions which
hold different /dev/fs configs, one for mirrored,
one for disk1 only and one for disk2 only. This means
the fossil and venti configs all refer to /dev/fs/XXX and will
work in any mode.
These configs liik like this:
so for normal, mirrored operation
mirror fossil /dev/sdE0/fossil /dev/sdF0/fossil
but for disk 1 only mode
inter fossil /dev/sdE0/fossil
The problem comes with /dev/fs/nvram for my keyfs
which is also 512 bytes. This appears to be empty
in the single disk mode of operation; it works
fine in mirrored operation
I have a suspicion that the problem is the nvram partition
is smaller than the interleave block size (defined in
/sys/src/9/port/devfs.c as 8kbytes.). Though I haven't
walked through the code to prove it.
Anyone noticed this?
what do other prople do - do you use mirroring or is
everyone using coraid raid servers now?
-Steve
reply other threads:[~2011-12-02 12:17 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=bb909f5842577098a187a158bbe18c12@quintile.net \
--to=steve@quintile.net \
--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).