🚀 go-pugleaf

moncam!loki@relay.eu.net writes:
> ... recenty some rather alarming things have been happening, things I
> have always assumed to be impossible on a clean filing system.  ...  I
> noticed that the first 1k or so bytes of the history file (the
> offending file, I assume), were found in one or two files randomly
> scattered around about the filing system.  ...  This problem does not
> seem to happen unless the disk fills up.  Has anyone ever witnessed
> such a thing?

We have a disk here which has an overflow problem.  Certain files, which
we have now captured and caged (renamed as .badXXX), seem to access recent
blocks from the host system cache rather than file disk blocks.  Don't ask
me how it happened, but some sequence of moves in SunOS 4.0 suninstall,
trying to modify disk partition sizes, seems to have caused the file
system to have been created slightly larger than the partition that holds
it.  Unfortunately, there is apparently no check against this in mkfs(8),
and no such check by fsck(8) either.  To see if this is the problem with
your partition, compare the dumpfs(8) "size" field (near the beginning of
the voluminous output) to the number of sectors reported for this
partition by dkinfo(8).  The size field should be exactly half the sectors
shown in the dkinfo output.  If it is larger, you have a problem; you'll
need to dump the file system and re-create it using mkfs(8) or newfs(8).

If you use dump(8) on a file system with this problem, you may get a
number of "(This should not happen)" messages as it tries to read the
offending files.

The problem only shows up when the file system gets full, because that's
when the tail end of the free list (containing these bogus blocks) finally
gets accessed, and the phantom blocks get allocated to files.  It has
nothing to do with brand of disk (ours is a Sun 327-MB drive, for
instance).

I suspect this problem may have been responsible for a number of strange
disk behaviors reported by other users over the years (an old Sun-Spots
article by Steve Simmons comes to mind, for instance); the problems may
have been blamed on disks or disk controllers instead of UNIX software.