Return to smash.8 CVS log

Up to [Research Unix] / researchv10dc / man / man8

Annotation of researchv10dc/man/man8/smash.8, revision 1.1

1.1     ! root        1: .TH SMASH 8
        !             2: .CT 1 sa_nonmortals
        !             3: .SH NAME
        !             4: smash \- rewrite bad disk sectors
        !             5: .SH SYNOPSIS
        !             6: .B /etc/smash
        !             7: .I device sector
        !             8: .SH DESCRIPTION
        !             9: .I Smash
        !            10: attempts to read the named (decimal, 512-byte)
        !            11: .I sector
        !            12: from the named
        !            13: .IR device ,
        !            14: and prints the error status from the read
        !            15: and the data read,
        !            16: in octal,
        !            17: regardless of the error status.
        !            18: It then prompts
        !            19: .LR write? ,
        !            20: to which there are three answers:
        !            21: .TP
        !            22: .B y
        !            23: Write the data back to the sector.
        !            24: .TP
        !            25: .B c
        !            26: Write zeros to the sector.
        !            27: .TP
        !            28: anything else
        !            29: Quit.
        !            30: .PP
        !            31: After the sector is written,
        !            32: it is read again
        !            33: and the cycle repeats.
        !            34: .PP
        !            35: Writing the sector,
        !            36: even if its contents could be correctly read,
        !            37: will recompute the error correcting code.
        !            38: This may make soft ECC errors vanish,
        !            39: and will recover what can be recovered
        !            40: (sometimes not much)
        !            41: from hard ECC errors.
        !            42: .SH SEE ALSO
        !            43: .IR rarepl (8)

This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.