On Thursday 09 December 2004 23:28, Mike Parker wrote:
> > [...] 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.

That doesn't really necessarily follow from the description I've seen of the 
problem.  If the blocks are scrambled when writing, you'll of course get the 
wrong thing back when you read.

But perhaps there's some more clear explanation of your problem that I haven't 
seen.