9front - general discussion about 9front
 help / color / mirror / Atom feed
From: Lorenzo Bivens <izaki@belaska.us>
To: "9front@9front.org" <9front@9front.org>
Subject: [9front] [PATCH] Doc contribution: CWFS with WORM on a separate drive
Date: Tue, 22 Jun 2021 05:47:12 +0000	[thread overview]
Message-ID: <CO1PR17MB5177ED25B5BF0E0D7DC07C1CB6099@CO1PR17MB5177.namprd17.prod.outlook.com> (raw)

Hi!

I have put together a few notes on how to setup cwfs with the cache and worm on separate disks. 
I think it could be a reasonable addition to the cwfs page of the docs page.

Patch inline below. Feedback is quite welcomed!

--- /tmp/docs.9front.org/.git/fs/object/a35de70a4d9d04e8af37ec5fd729cf6d9bf98230/tree/cwfs.md
+++ cwfs.md
@@ -87,3 +87,43 @@
 to confirm. `wsize * 16000` is the size of your WORM.
 
 No refunds
+
+CWFS with WORM on a separate drive
+----------------------------------
+
+### What you do is what you get
+These instructions assume you want to set up a CWFS on two drives one containing
+the cache filesystem, and the other containing the WORM
+
+This process has been tested on MBR installations, but should be extrapolable 
+to GPT as well with minor changes. (please report results)
+
+Note that the instructions won't work unless you have read them first
+
+### Initialize the disks
+For this examble sd00 will be our cache drive, sd01 will be our WORM
+
+Assuming your drives are new, for a MBR partitioning scheme, you want to first 
+create a MBR partition table. (see end note if using GPT)
+
+	disk/mbr -a /386/mbr /dev/sd00/data 
+	disk/mbr -a /386/mbr /dev/sd01/data
+
+You need to add a plan9 partition to both disks, otherwise the installer will not see them
+
+	disk/fdisk -baw /dev/sd00/data 
+	disk/fdisk -baw /dev/sd01/data
+
+Now it is time to subdivide the plan9 partitions on both disks. We will then subpartition 
+the cache, and worm disks
+
+	disk/prep -bw -a^(9fat nvram other fscache) /dev/sd00/plan9
+	disk/prep -bw -a fsworm /dev/sd01/plan9
+
+The steps to make this layout work on GPT partitioned drives should be similar, 
+skipping the mbr initialization, and using disk/edisk instead of fdisk.
+
+### Finally
+Start your installation as usual: select cwfs64x as your filesystem, 
+skip partdisk and prepdisk. When going through the mountfs step, 
+make sure to point to the right partitions on each function.

             reply	other threads:[~2021-06-22  9:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-22  5:47 Lorenzo Bivens [this message]
2021-06-22 12:07 ` Sigrid Solveig Haflínudóttir

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=CO1PR17MB5177ED25B5BF0E0D7DC07C1CB6099@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).