From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <9dc713f8017f9ffce2797522dcf318df@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] kenfs config? (was: OT: scsi sense error code hardware
Date: Tue,  3 Oct 2006 17:19:38 -0400
From: geoff@plan9.bell-labs.com
In-Reply-To: <200610032013.k93KD9m20820@zamenhof.cs.utwente.nl>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Topicbox-Message-UUID: c4b03e22-ead1-11e9-9d60-3106f5b1d025

Right, you could just configure the cache as mirrored disks and
recover main.  The mirror device does not copy new devices when they
are added to a mirror; you'd need to copydev first (or boot as a cpu
server and use dd) to copy the original disk to its mirror disks).

You should only use "config w0" when you initialise the configuration.
Thereafter, the file server kernel reads that configuration (from w0
in this case, which name it gets from plan9.nvr) at start-up and
merges any changes due to config commands that you then type.  Typing
a "filsys" command for an existing file system will replace the old
definition; "filsys scratch" would delete any definition for a file
system named "scratch"; and declaring a file system with a name as yet
unknown will add the file system.

The panic after copydev is indeed to force a reboot and give an
opportunity for reconfiguration.

I understand your caution.  There was a period when I was configuring
kenfs daily or pretty close to it, but that's certainly unusual.