From: "Brian L. Stuart" <blstuart@bellsouth.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Mirrorarenas in p9p
Date: Thu, 31 Jul 2008 15:30:12 +0000 [thread overview]
Message-ID: <073120081530.19155.4891DA840000F21F00004AD322243429029B0A02D2089B9A019C04040A0DBF9B9D0E9A9B9C040D@att.net> (raw)
In-Reply-To: <facd3da3788cee374525905f460e4fa4@coraid.com>
> > - Is this going to cause any problems?
> > - Is there a better way to handle this?
>
> could you use disk/prep instead of disk/fdisk?
> prep should work in this situation as long as the
> sector size on both drives is the same.
I don't think so. Unless it's been added recently,
p9p doesn't have prep. But even if it did, the
subpartitions it creates wouldn't be visible to
Linux, so I wouldn't have any way to name them
for mirrorarenas. At least that's the way I
understand it. It's certainly possible I'm
mistaken, however.
BTW the reason it's p9p on Linux instead of an
actual Plan 9 install is that the particular
hardware I scrounged has one of those SCSI
controllers that can do RAID but has no driver
in Plan 9. I did set it up before 9vx, though.
So maybe I could rethink some things and build
it all around that. It'd be a little weird
because it's an archive server for UNIX machines
using vbackup. So it runs vnfs to serve the
dumps. But I suppose I could run venti in 9vx
and vnfs in Linux and, in principle, I think
it would work. Or I could probably compile
vnfs under Plan 9 and run both under 9vx.
Sorry to ramble. I'm brainstorming as I
write...
Thanks,
BLS
next prev parent reply other threads:[~2008-07-31 15:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <073120081453.4828.4891D1D2000C4C1E000012DC22243429029B0A02D2089B>
2008-07-31 14:58 ` erik quanstrom
2008-07-31 15:30 ` Brian L. Stuart [this message]
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
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=073120081530.19155.4891DA840000F21F00004AD322243429029B0A02D2089B9A019C04040A0DBF9B9D0E9A9B9C040D@att.net \
--to=blstuart@bellsouth.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).