9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: geoff@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	[thread overview]
Message-ID: <9dc713f8017f9ffce2797522dcf318df@plan9.bell-labs.com> (raw)
In-Reply-To: <200610032013.k93KD9m20820@zamenhof.cs.utwente.nl>

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.



  reply	other threads:[~2006-10-03 21:19 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-03 13:10 [9fans] OT: scsi sense error code hardware error 40 83? Axel Belinfante
2006-10-03 18:17 ` geoff
2006-10-03 20:13   ` [9fans] kenfs config? (was: OT: scsi sense error code hardware error 40 83?) Axel Belinfante
2006-10-03 21:19     ` geoff [this message]
2006-10-17 15:55       ` [9fans] kenfs config? (was: OT: scsi sense error code hardware Axel Belinfante
2006-10-17 20:18         ` geoff
2006-10-17 21:05           ` Axel Belinfante
2006-10-17 21:35             ` geoff
2006-10-17 23:55               ` Axel Belinfante
2006-10-03 20:20   ` [9fans] gs Charles Forsyth
2006-10-03 20:39     ` geoff
2006-10-03 20:41     ` Francisco J Ballesteros
2006-10-03 20:48     ` Jack Johnson
2006-10-03 21:37       ` LiteStar numnums
2006-10-03 22:07         ` Andy Newman
2006-10-04  2:18       ` jmk
2006-10-06  0:00         ` Bruce Ellis

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=9dc713f8017f9ffce2797522dcf318df@plan9.bell-labs.com \
    --to=geoff@plan9.bell-labs.com \
    --cc=9fans@cse.psu.edu \
    /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).