This command investigates free space in /, /usr,
and /tmp filesystems to determine whether sufficient
disk blocks and inodes exist in each of potentially 3 filesystems.
The default tests that idspace performs are as follows:
Verify that the root filesystem (/)
has 400 blocks more than the size of the current /unix.
This verifies that a device driver being added to the current
/unix can be built and placed in the root directory.
A check is also made to insure that 100 inodes exist
in the root directory.
Determine whether a /usr filesystem exists.
If it does exist, a test is made that 400 free blocks
and 100 inodes are available in that filesystem.
If the filesystem does not exist an error is returned,
but since files used by the reconfiguration process will be
created in the root file system, space requirements are
covered by the test above.
Determine whether a /tmp filesystem exists.
If it does exist, a test is made that 400 free blocks
and 100 inodes are available in that filesystem.
If the filesystem does not exist an error is returned,
but since files used by the reconfiguration process will be
created in the root file system, space requirements are
covered by the test above.
The command line options are:
-iinodes
This option overrides the default test for 100 inode in all of the
idspace checks.
-rblocks
This option overrides the default test for /unix
size + 400 blocks when checking the root (/) filesystem.
When the -r option is used, the /usr
and /tmp
filesystems are not tested unless explicitly specified.
-ublocks
This option overrides the default test for 400 blocks when checking the
/usr filesystem.
When the -u option is used, the root (/)
and /tmp
filesystems are not tested unless explicitly specified.
If /usr is not a separate filesystem, an error is reported.
-tblocks
This option overrides the default test for 400 blocks when checking the
/tmp filesystem.
When the -t option is used, the root (/)
and /usr filesystems are not tested unless explicitly specified.
If /tmp is not a separate filesystem, an error is reported.
Exit values
An exit value of zero indicates success.
If insufficient space exists in a filesystem
or an error was encountered due to a syntax or format error,
idspace will report a message.
All error messages are designed to be self-explanatory.
The specific exit values are as follows:
0
success
1
command syntax error, or needed file does not exist
2
filesystem has insufficient space or inodes
3
requested filesystem does not exist
(-u and -t options only)