9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Geoff Collyer <geoff@collyer.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] adding storage to ken's fs
Date: Mon,  2 Feb 2004 19:50:46 -0800	[thread overview]
Message-ID: <5d408ee5203752b249ce270e2a105bde@collyer.net> (raw)
In-Reply-To: <Pine.LNX.4.30.0402021110490.1127-100000@athena>

> filsys main cw0f(w1.1w1.0.0w1.1.1)

I think you want

	filsys main cw0f(w1w1.<0-1>.0)

That is, wT is scsi adaptor 0, target (a.k.a.  unit) T, lun 0; wA.T.L
is adaptor A, target T, lun L. lun is almost always 0 (some jukeboxes
use, or can be configured to use, non-zero luns).  wT.L is adaptor 0,
target T, lun L, which turns out to be rarely useful.  fsconfig(8) has
the whole story.

(You may also have to issue

	filsys dump o

again afterward; I'm not sure.  I always do this after redefining a cw
main since the dump is derived from the worm part of the cw
declaration.)

I believe that this should grow your fake worm, but Charles or Nigel
probably have more experience with this.  I've changed cache disks and
added and removed (as-yet-unwritten) optical disks, and the fs kernel
always seems to automatically and correctly resize the cache or the
worm as appropriate.  On the other hand, I'm not sure how the
fake-worm's bitmap would interact with adding more space.

> Any other tips for doing this without shooting myself in the foot?

or shooting yourself in the root. ☺  Obviously a dump to CD of your
own files first wouldn't be a bad idea.  Type carefully on the fs
console and double-check commands before pressing `return'.



  reply	other threads:[~2004-02-03  3:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-02 16:28 Sam
2004-02-03  3:50 ` Geoff Collyer [this message]
2004-02-03 11:02   ` Charles Forsyth

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=5d408ee5203752b249ce270e2a105bde@collyer.net \
    --to=geoff@collyer.net \
    --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).