> [...] I did a very quick audit of the FFS code and found what looks
> like a serious truncation problem.  Attached is a diff that I think
> will fix it.

This fix actually does not fix my problem at all.  Looking at the
greater context, this is not surprising, because this function is
called only when new blocks are being allocated.  My problem strikes
when reading existing, valid (per fsck), on-disk data structures.

I'm going to take my own look at the code paths in question and see
what I can see; for something like this, more eyes means a better
chance of finding it....

/~\ The ASCII				der Mouse
\ / Ribbon Campaign
 X  Against HTML	       mouse@rodents.montreal.qc.ca
/ \ Email!	     7D C8 61 52 5D E7 2D 39  4E F1 31 3E E8 B3 27 4B