Problem
Running fsck(ADM) on a filesystem bigger than 2GB (HTFS), with flags of -n and -ofull gives the following error:
DANGER: Filesystem being checked is larger than the device in which it is stored (/dev/root). The filesystem is 6388258K while the device is 2097152K. Backup filesystem and recreate as soon as possible.
Leaving off the -n (no write) flag doesn't produce the error message.
Cause
This may indicate a real problem (See SOLUTIONS) or it could
be a result of a problem with fsck(ADM) for HTFS. fsck(ADM)
uses a special "block mode" ioctl(S) to allow it to seek to
offsets >2GB in a device. This ioctl(S) will fail when fsck(ADM)
is operating read-only (`fsck(ADM) -n` or fsck(ADM) on a write
protected device). Since the ioctl(S) fails, fsck(ADM) can only
seek to 2GB in the device.fsck(ADM) figures out physical device size by doing a binary
search of possible seek offsets. Having failed to turn on
block mode, this binary search determines a size of 2GB. The
logical filesystem size (from the superblock) is much larger,
so it complains. Solution
To tell if this is a real problem run another fsck(ADM) without -n.
If the fsck(ADM) without -n still complains, and the device isn't
physically write protected, the filesystem is too big; follow
fsck(ADM)'s advice.If fsck(ADM) without -n doesn't give this error message, then you may safely ignore this message.
This has been reported to SCO Engineering. Bugreport ID is LTD-245-1998.