SDFFSCK(1M) — HP-UX

Series 300, 800 Only

NAME

sdffsck − SDF file system consistency check, interactive repair

SYNOPSIS

sdffsck [−y] [−n] [−s] [−d] SDFdevice ...

DESCRIPTION

Sdffsck is intended to mimic the series 500 implementation of fsck[SDF](1M).

Sdffsck checks and interactively repairs inconsistent conditions for SDF file systems. If the file system is consistent, then the number of files, the number of blocks used, the number of blocks free, and the percent of volume unused are reported. If the file system is inconsistent, the operator is prompted for concurrence before each correction is attempted. Note that many corrective actions will result in some loss of data. The amount and severity of the loss can be determined from the diagnostic output. The default action for each consistency correction is to wait for the operator to respond yes or no. If the operator does not have write permission, sdffsck defaults to −n.

Sdffsck makes multiple passes over the SDF file system, so care should be taken to ensure that the SDF device is quiescent.

The following flags are interpreted by sdffsck:

−y Assume a yes response to all questions asked.

−n Assume a no response to all questions asked; do not open the file system for writing.

−s Ignore the actual free list and unconditionally reconstruct a new one. This option is useful in correcting multiply claimed blocks when one of the claimants is the free list. When using this option, the number of unclaimed blocks reported by sdffsck includes all the blocks in the free map. This can produce extensive output if −d is also selected.
−s should only be selected after a previous sdffsck indicates a conflict between a file and the free map. After sdffsck −s has executed, the integrity of the conflicting file(s) should be checked.

−d Dump additional information. The more d’s that are present, the more information that is dumped. You may specify up to five d’s. Using more than two, however, can result in an overwhelming amount of output.

Sdffsck also recognizes, and ignores, the −S and −t options found in other versions of fsck. An appropriate warning is printed. The diagnostics are intended to be self-explanatory.

SDFdevice is a device file name describing the device on which the SDF file system to be checked resides (e.g., /dev/rdsk/c1d1s4).

Error messages from sdffsck are written to stderr. Information generated because of the −d option and normal output is written to stdout; both are unbuffered.

Inconsistencies checked include:

1. Blocks claimed by more than one inode, or by the free list;

2. Blocks claimed by an inode or the free list outside the range of the file system;

3. Incorrect link counts;

4. Blocks not accounted for anywhere;

5. Bad inode format;

6. Directory checks:

Files pointing to unallocated inodes;
Inode numbers out of range;
Multiply linked directories;
Link to the parent directory.

Orphaned files (allocated but unreferenced) with non-zero sizes are, with the operator’s concurrence, reconnected by placing them in the lost+found directory on the SDF file system. The name assigned is the inode number. The only restriction is that lost+found must exist in the root of the SDF file system being checked, and must have empty slots in which entries can be made. This is accomplished by executing

sdfmkdir SDFdev:/lost+found

(using the name of the SDF device for SDFdev).

Orphaned directories and files with zero size are, with the operator’s concurrence, returned directly to the free list. This will also happen if the lost+found directory does not exist.

WARNINGS

Sdffsck cannot check devices with a logical block size greater than 4096.

AUTHOR

Sdffsck was developed by HP.

Museum