SYSTEM UTIUTIES diskrepair

NOTE

Thefirst time diskrepair reports an 110 error, answer no to the offer to continue and immediately rerun diskrepair. It is possible, though unlikely, that the 110 error is a soft one and will not recur.

Error updating SIR. Disk is bad!

Diskrepair encountered an I/O error when it tried to make the necessary changes in the System Information Record. The user should try again to execute diskrepair. If the error persists, the user cannot salvage any of the data on the disk.

/etc/blockcheck is invalid.

The version of the blockcheck command is not the correct one.

/etc/fdncheck is invalid.

The version of the fdncheck command is not the correct one.

Fdncheck terminated abnormally.

Fdncheck received a program interrupt from the operating system. The user cannot determine the source of such an error; however, it is not indicative of a problem with either diskrepair or the device. Diskrepair should be rerun, for the problem may not recur.

Intentional system stop. Reboot system.

If the System Information Record of the root device must be updated, diskrepair kills all tasks running on the system and locks up the system so that no new tasks can begin. It then modifies the SIR. This procedure is necessary to prevent conflicts between the written data and similar data kept in memory. After updating the SIR, diskrepair stops the system and prints this error message. The user must reboot the system before proceeding.

No device specified.

The user did not specify a device on the command line.

No such device.

The user specified a nonexistent device on the command line.

Not a block device.

Diskrepair can only operate on block devices.

Output directed to device under test.

When testing the structure of a disk, it is impractical to try to redirect the output (the results of the test) to a file on the disk being tested. The user should reexecute diskrepair without redirecting the output or redirecting it to a different, mounted device.

Permission denied.

A user who executes diskrepair without the "n" option must have both read and write permission on the specified device. A user who executes diskrepair with the "n" option needs only read

Problems encountered. Diskrepair should be rerun.

Diskrepair may encounter more problems than it can fix during one run. For example, it can only handle a certain number of duplicate or out-of-range blocks. If diskrepair cannot fix all the errors it encounters, or if it encounters an I/O error but continues operation, it prints this error message when it finishes.

Invalid option: <char>

The option specified by <char> is not a valid option to the diskrepair command.

Unmount error: <error num>

Diskrepair encountered some problem other than a busy device when it tried to unmount the device. The accompanying error number is the number of the 4404 error that caused the failure.

The user should consult the operating system manual for an explanation of the error.

SEE ALSO

blockcheck fdncheck

SYSTEM UTILITIES fdncheck

fdncheck

Check the integrity of the structure of the file descriptor nodes (fdns) on the specified disk.

SYNTAX

/etc/fdncheck <dev name>

DESCRIPTION

The fdncheck command checks the integrity of the structure of the file descriptor nodes (fdns) on the specified disk. An fdn contains all the infonnation that the operating system needs to know about a file.

This information includes, but is not limited to, the type of file, the owner of the file, the size of the file, and the addresses of all the blocks that are a part of the file. The fdncheck command locates problems such as unreferenced files, directory entries with invalid associated files, and so forth.

This command is primarily intended for use by the diskrepair utility, which calls it. It may also be used on its own. However, fdncheck can only check the structure of the disk; it cannot repair it. If the output from the command suggests that the structure of the fdns is damaged, the user should execute diskrepair on the disk.

The fdncheck command should be executed only when no other tasks are active on the system.

Otherwise, the results are unpredictable.

ARGUMENTS

<dev name> The name of the device to check. It must be a block device.

EXAMPLES

/etc/fdncheck /dev/floppy

Checks the structure of the fdns on the disk in the floppy drive.

SEE ALSO

blockcheck diskrepair

makdev

Create a special type of file, representing a device.

SYNTAX

/etc/makdev <file name> <dey_type> <maj_dev_num> <min dey num>

DESCRIPTION

The makdev command creates a special type of file which represents a device. This type of file allows the user to access the device drivers for the corresponding physical device. Only the system user may invoke this command.

The major device numbers are listed in Table 3-2.

ARGUMENTS

<file name>

Table 3-2 Major Device Numbers

Number Device

0 Block:

0 ConsolelttyOO

1 Memory

1 PttyOO-ptty(nn)

2 Null

3 Floppy char 4 Disk char

5 Sound

6 Printer

7 Communication port 8 Tape char

The name of the file to create. For a block device, the last component of the file name must consist of a string of letters. For a character device, the last component of the file name must consist of the same string of letters, followed by the letter" c" .

A letter designating whether the device is a block device, (b); a character device, (c); or a ptty device, (p).

A number which tells the operating system which set of device drivers to use for the specified device.

A number which tells the operating system which physical device to associate with <file name>.

SYSTEM UTILITIES