9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: forsyth@caldo.demon.co.uk
To: 9fans@cse.psu.edu
Subject: Re: [9fans] fs (config) questions
Date: Fri, 13 Apr 2001 23:41:08 +0100	[thread overview]
Message-ID: <20010413224351.96123199C0@mail.cse.psu.edu> (raw)

[-- Attachment #1: Type: text/plain, Size: 1155 bytes --]

each time i've considered that question (each time
i've configured a new file server) i've eventually decided
in favour of using the pseudo-worm driver.
it isn't more resilient in the face of certain crashes
but it might be slightly more likely to detect an inconsistency
sooner rather than later (or at least more cleanly).
i could be wrong but i suspect a few supporting commands rely on getting
a read error for blocks not yet written (cwcmd prchain might be one).

i'm glad i did keep the bitmap the last time, for another reason.
the written-block bitmap also turned out to be quite
useful when copying the existing structure to a real
worm jukebox, since it said which blocks had actually
been written, and helped to set precise limits for the copy.

another useful hint when copying a
pseudo-worm to a new file server with a real jukebox
and a new set of cache discs with a different structure is to do
	cwcmd savecache
on the file server, and {disk/exsort -w} before
starting the copy.  that way, cwcmd loadcache
will reload the cache on the new file server
with much less jukebox activity (and that's an understatement).


[-- Attachment #2: Type: message/rfc822, Size: 2273 bytes --]

From: "Russ Cox" <rsc@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] fs (config) questions
Date: Fri, 13 Apr 2001 14:08:38 -0400
Message-ID: <200104131808.OAA20972@smtp2.fas.harvard.edu>

	yes it is possible, but not quite that easy (yet).  i've done it several times,
	using a specially-modified file server kernel to initialise the
	bitmap for the pseudo-worm area
	(after that the normal code is happy to include and write to the extended space).

is there a reason to use the pseudo-worm driver at all?
as far as i could tell, it's just making sure that blocks don't
get written twice.  that's important, i guess, assuming the
cached worm driver is debugged, i'd expect to be
able to use `cw1w2' to the same effect as `cw1fw2' except
that the former doesn't have the bitmap and thus can be
lifted from one disk onto another without a special kernel.

am i missing something?  (probably.)

russ

             reply	other threads:[~2001-04-13 22:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-13 22:41 forsyth [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-04-13 18:08 Russ Cox
2001-04-13  8:47 forsyth
2001-04-11 20:20 Axel Belinfante
2001-04-12 19:44 ` Axel Belinfante

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=20010413224351.96123199C0@mail.cse.psu.edu \
    --to=forsyth@caldo.demon.co.uk \
    --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).