From: Lorenzo Bivens <izaki@belaska.us>
To: "9front@9front.org" <9front@9front.org>
Subject: [9front] Disk Mirroring, or disk composition using fs(3)
Date: Thu, 17 Jun 2021 23:54:05 +0000 [thread overview]
Message-ID: <CO1PR17MB5177146B05BA4D45A140A67EB60E9@CO1PR17MB5177.namprd17.prod.outlook.com> (raw)
Hi!
I am attempting to setup a couple of disks as mirrors to store a cwfs' fsworm partition. I am operating under the assumption that an fs(3) made disk file operates as any other disk.
Starting with two identical blank disks, here is my current process:
echo mirror md0/data /dev/sd01/data /dev/sd02/data >/dev/fs/ctl
disk/mbr -m /386/mbr /dev/md0/data # adding mbr to the mirror set correctly adds mbr to both disks
echo part md0/plan9 /dev/md0/data 0 end >/dev/fs/ctl # correctly adds a partition to both disks
echo part md0/fsworm /dev/md0/plan9 0 end >/dev/fs/ctl # adds the fsworm subpartition
So far, so good. Now let's try the install
configfs... cwfs64x
partdisk... setup my cache drive
prepdisk... slice the cache drive with 9fat, nvram, other, and fscache
mountfs:
- /dev/sd00/fscache as fscache
- /dev/md0/fsworm as worm (manual input since no suggestions are made)
- /dev/sd00/other as other (and I am not even sure I want this...)
ream the system? (mutual assured destruction) yes
a series of
wrenwrite: block out of range w"/dev/md0/fsworm"(2)
wrenread: block out of range w"/dev/md0/fsworm"(2)
....
w"/dev/md0/fsworm" block 2 WORM SUPER BLOCK READ FAILED
...
and the rest is consequence of that
I suspect this could be a problem of assumptions. If anyone has experience with a similar disk layout... how did you make it work?
Thanks!
next reply other threads:[~2021-06-18 5:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-17 23:54 Lorenzo Bivens [this message]
2021-06-18 8:02 ` Noam Preil
2021-06-18 19:09 ` Lorenzo Bivens
2021-06-18 8:06 ` Noam Preil
2021-06-18 21:22 ` [9front] " Anthony Martin
2021-06-21 5:20 ` Lorenzo Bivens
2021-06-21 5:34 ` Lorenzo Bivens
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=CO1PR17MB5177146B05BA4D45A140A67EB60E9@CO1PR17MB5177.namprd17.prod.outlook.com \
--to=izaki@belaska.us \
--cc=9front@9front.org \
/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).