Relational Database Responses

[Guy Harris]

> 13. When doing a file system check(fsck) on the onyx "Possible file size
>     error <inode #>"  shows up on system containing the unify dbms.

This ain't a bug in UNIFY; it's arguably a bug in "fsck".  This error
message is printed if the number of blocks implied by the file size
doesn't match the actual number of blocks allocated to the file.
Unfortunately, if the file has "holes" (i.e., sections in the middle of the
file with no blocks allocated to it), these numbers won't agree.
"Holes" are a well-known - and even documented - feature (deliberate
feature - sparse files can save lots of disk space) of UNIX ever since
V6 (although they didn't work as well in V6 as in post-V6 systems - reading
a "hole" in V6 caused the blocks to be allocated).

I suspect the "correct" answer is to compare the number of blocks implied
by the file size with the number of blocks implied by the block number
of the highest allocated block (i.e., if the file had no holes, this would
be the number of blocks in the file).

	Guy Harris
	{seismo,ihnp4,allegra}!rlgvax!guy