FSCK(8)

NAME
lde - a file system viewer/editor for Linux

SYNOPSIS
lde device

DESCRIPTION
lde is a curses (ncurses) interface for the Linux MINIX filesystem. One day it will support file system editing, ala Norton utilities, but for now it's main use is to poke around the file system looking for bits and pieces of a file which you may have erased. It is by no means an unerase, unless you get incredibly lucky. The lde main screen displays the file system's superblock in the workspace window. The header window will be the same for all modes and indicates the program name and version, the device, the current selected inode, and the current selected block. There are also nine digits which indicate the status of a bogus inode which can be used for file recovery. A digit means the inode block entry has not been filled yet, a minus sign indicates that it has been filled. From the main screen, use the case insenitive keys (these options are valid from any mode):

    i   - to enter inode mode

    b   - to enter block mode

    r   - to enter recover mode

    s   - return to super block mode

    q   - to quit

    ^L  - to repaint the screen
Inode mode: Once in inode mode, the current inode will be displayed in the workspace window.

    ^N PG_DOWN DOWN_ARROW
        - make next inode the current inode

    ^P PG_UP UP_ARROW
        - make previous inode the current inode

    RT_ARROW
        - select next block (from those indexed by the inode, the cursor will follow your selection)

    LT_ARROW
        - select previous block

    u   - toggle viewing of all/unused inodes

    0-8 - switch to block mode viewing block indexed by number, 7 is the indirect block, eight is the double indirect block

    B   - switch to block mode, examining block under cursor

    b   - switch to block mode, examining current block (displayed in status line)

    R   - switch to recover mode, copy current inode block information into recovery inode

    #   - this will prompt the user to enter a number and it will then make that the current inode. The number may be entered as hexidecimal (leading 'x', '0x', or '$'), octal (leading ''), or decimal.
Block Mode: In block mode, the current block will be displayed in hexidecimal and ASCII. The numbers along the left hand side of the screen are hexidecimal offsets from the beginning of the block. As much of the block as possible will be displayed. If the block is marked unused, the central row of ':' will spell out NOT USED.

    RT_ARROW
        - display next chunk of this block

    LT_ARROW
        - display previous chunk of this block

    ^N PG_DOWN DOWN_ARROW
        - make next block the current block

    ^P PG_UP UP_ARROW
        - make previous block the current block

    u   - toggle viewing of all/unused inodes

    0-8 - tag this block to be recovered. The nine blocks represent the same nine blocks which would be used in an inode. 0-6 are direct blocks, 7 is the indirect block, and 8 is the double indirect block. One day there may be an option for more than seven direct blocks to make recovery easier. When a block is tagged, the status line will reflect this. To untag a block, go to recover mode and set the block's pointer to zero.

    #   - this will prompt the user to enter a block number. The numbers may be entered in the same format described in inode mode.
Recover Mode: In recover mode, the tagged blocks are displayed and may be edited by hand. When they are correct the user can dump the file. The user is prompted for a filename which can be 80 chars, the default file is "./RECOVER.file".

    0-8 - will prompt the user to enter a numberic value for the specifed block index. The format of the input should be the same as that described in inode mode.

    c   - check the "recover-ability" of the file.

    r   - write out the recovered file
for more information.

SEE ALSO
fsck(8), mkfs(8), efsck(8), emkfs(8), reboot(8)

DIAGNOSTICS
If the device does not exist, lde will print "unable to read super block". If the device exists, but is not a MINIX file system, lde will print "bad magic number in super-block".

AUTHOR
Scott D. Heavner (sdh@po.cwru.edu) -- based largely on fsck by Linus Torvalds (torvalds@cs.helsinki.fi)