From: "Russ Cox" <rsc@swtch.com>
To: 9fans@9fans.net
Subject: Re: [9fans] Mirrorarenas in p9p
Date: Thu, 31 Jul 2008 18:13:47 -0400 [thread overview]
Message-ID: <20080731221159.A22791E8C3B@holo.morphisms.net> (raw)
In-Reply-To: <073120081952.25804.48921807000DA385000064CC22193100029B0A02D2089B9A019C04040A0DBF9B9D0E9A9B9C040D@att.net>
>> Also, if you do create a Plan 9 partition and
>> then prep it to make subpartitions (you'd have
>> to use 9vx, copying the binaries from sources),
>> then p9p venti can handle those partition names
>> too: /dev/sda1:arenas assuming /dev/sda1 is a
>> Plan 9 fdisk partition containing a subpartition
>> named arenas.
>
> So here's what I ended up with. I installed 9vx on
> the machine and used that to partition the big
> drive: one fairly big partition with 4 subpartitions
> for the 4 arena disks already on the machine. The
> p9p mirrorarenas didn't like the partition name
> notation. It calls initpart which calls parsepart
> which seems to only like the numeric range notation.
> But running the Plan 9 mirrorarenas in 9vx works
> just fine. So I'm pretty much where I want to be
> for now.
It should be there as of HG revision 2825 (July 3).
The particular file contents that I expect are at
http://swtch.com/go/venti-plan9-partitions
It's at the bottom of the file.
In addition to /dev/sda1:arenas you can say
/dev/sda:arenas -- the code parses the fdisk table
to find the Plan 9 partition too (but it's also happy
if you give it the Plan 9 partition directly).
Using 9vx is fine, of course, but this is one less
moving piece in your mirroring scripts.
Russ
next prev parent reply other threads:[~2008-07-31 22:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-31 14:53 Brian L. Stuart
2008-07-31 16:06 ` Russ Cox
2008-07-31 19:52 ` Brian L. Stuart
2008-07-31 22:13 ` Russ Cox [this message]
[not found] <073120081453.4828.4891D1D2000C4C1E000012DC22243429029B0A02D2089B>
2008-07-31 14:58 ` erik quanstrom
2008-07-31 15:30 ` Brian L. Stuart
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=20080731221159.A22791E8C3B@holo.morphisms.net \
--to=rsc@swtch.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).