From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <72a27d6c7aba3d47f462a0a6477e9e2f@collyer.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Bad Karma with old kit
Date: Sun,  5 Jun 2005 14:49:35 -0700
From: geoff@collyer.net
In-Reply-To: <9fad8e46180480a87bb08e10ebd3adcc@proxima.alt.za>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Topicbox-Message-UUID: 5c52492a-ead0-11e9-9d60-3106f5b1d025

Usually if the block size is wrong, the magic number for the
configuration block is also wrong (since the configuration block is
then looked for at the wrong offset), which should cause a panic or
other drastic failure.

dat.h looks pretty much the same in the 64-bit fs.  The block size is
a truly fundamental constant of the file server implementation;
changing it currently requires recompilation because the block size,
and constants derived from it, are used in array declarations and the
like.  There are ways that one could work around it, with some
contortions in the code.  kfs does, after all, but kfs had to (or at
least did) change the on-disk representation to make this feasible.