From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <f263b66c926f04bb3490e066207fd8cc@collyer.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] fs hardware configuration
From: Geoff Collyer <geoff@collyer.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Date: Fri, 29 Nov 2002 15:13:41 -0800
Topicbox-Message-UUID: 2a54f0da-eacb-11e9-9e20-41e7f4b1d025

The latest file server code and manual pages on sources include IDE
support, the mirror device and a few other small changes.  So the
latest CD image should include them too.  The new fsconfig(8) includes
a more complex real-life example than before.

My file server with 4 IDE disks uses this configuration:

	config h0
	service fs
	filsys main c{p(h0)0.25p(h2)0.25}f{p(h0)25.75p(h2)25.75}
	filsys dump o
	filsys spare h1
	filsys other h3
	ipauth 0.0.0.0
	ipsntp 10.9.0.3
	ip0 10.9.0.1
	ipgw0 10.9.0.254
	ipmask0 255.255.0.0
	end

It's evolved over time and so isn't necessarily the best use of the
drives.  main uses the first 25% of h0 as cache and mirrors it to the
first 25% of h2 (h1.0.0).  It also uses the rest of h0 as a fake worm
and mirrors it to the rest of h2.

For your hardware, I'd suggest a fake worm on one IDE drive, mirrored
to the second, with one SCSI drive as "other" and the other as cache.
So something like this:

	config h0
	service fs
	filsys main cw0f{h0h2}
	filsys dump o
	filsys other w1
	ipauth 0.0.0.0
	ipsntp 10.9.0.3
	ip0 10.9.0.1
	ipgw0 10.9.0.254
	ipmask0 255.255.0.0
	ream main
	ream other
	end

This assumes that you make the IDE drives masters on separate
controllers.  Of course, you only ream the file systems once, to
initialise them.