9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Geoff Collyer <geoff@collyer.net>
To: 9fans@collyer.net
Subject: [9fans] jukebox configuration changes
Date: Fri,  1 Nov 2002 01:43:59 -0800	[thread overview]
Message-ID: <71ed15d151980331661063c9918daaeb@collyer.net> (raw)

I've just modified the file server kernel to cope with different
DSIZEs (optical disc sizes) per jukebox and even per disc.  It's now
also possible to change FIXEDSIZES in /sys/src/fs/*/9*.c rather than
having to edit dev/juke.c before compiling each distinct kernel.

The way it used to work was that DSIZE was the size in RBUFSIZE-byte
blocks of each optical disc *side*.  However, it is possible to use
discs of different sizes within a single jukebox: you set FIXEDSIZES
to 0 and pay with a delay at each boot while the file server pulls
each disc side in and asks the drive how big it is.  It's probably
wiser to use discs of the same size and set FIXEDSIZES to 1, which
makes the file server just look at one disc and assume that all the
sides are the size of its.  So DSIZE was only used for computing the
statistics that "statw" prints on the console, for working out sizes
in the cache save and restore commands, and in the implementation of
"check touch".  Those operations could be led astray if DSIZE wasn't
the size in Plan 9 blocks of all the optical discs in all jukeboxes on
a given file server.  If one wanted to put a jukebox with 5.2GB discs
and one with 2.6GB discs on the same file server, it wouldn't work
perfectly.

DSIZE is gone.  It's now possible to mix jukeboxes with discs of
different sizes, and even, if you're willing to put up with the
delays, to use discs of different sizes within a single jukebox, and
everything should now work right.

The whole thing compiles but I want to test it tomorrow (after the
third jukebox arrives) before I offer the code to anyone else.


             reply	other threads:[~2002-11-01  9:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-01  9:43 Geoff Collyer [this message]
2002-11-02  9:37 Geoff Collyer

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=71ed15d151980331661063c9918daaeb@collyer.net \
    --to=geoff@collyer.net \
    --cc=9fans@collyer.net \
    /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).