The OpenNET Project / Index page

[ новости /+++ | форум | wiki | теги | ]

Интерактивная система просмотра системных руководств (man-ов)

 ТемаНаборКатегория 
 
 [Cписок руководств | Печать]

fsck.jfs (8)
  • >> fsck.jfs (8) ( Linux man: Команды системного администрирования )
  •  

    NAME

    fsck.jfs 
    
    - initiate replay of the JFS transaction log, and check and repair a JFS formatted device
    

     

    SYNOPSIS

    fsck.jfs [ -afnopvV ] device

     

    DESCRIPTION

    fsck.jfs is used to replay the JFS transaction log, check a JFS formatted device for errors, and fix any errors found.

    device is the special file name corresponding to the actual device to be checked (e.g. /dev/hdb1).

    fsck.jfs must be run as root.

     

    WARNING

    fsck.jfs should only be used to check an unmounted file system or a file system that is mounted READ ONLY. Using fsck.jfs to check a file system mounted other than READ ONLY could seriously damage the file system!

     

    OPTIONS

    If no options are selected, the default is -p.
    -a
    Autocheck mode - Replay the transaction log. Do not continue fsck processing unless the aggregate state is dirty or the log replay failed. Functionally equivalent to -p. Autocheck mode is typically the default mode used when fsck.jfs is called at boot time.
    -f
    Replay the transaction log and force checking even if the file system appears clean. Repair all problems automatically.
    -n
    Open the file system read only. Do not replay the transaction log. Report errors, but do not repair them.
    -o
    Omit the replay of the transaction log. This option should not be used unless as a last resort (i.e. the log has been severely corrupted and replaying it causes further problems).
    -p
    Automatically repair ("preen") the file system. Replay the transaction log. Do not continue fsck processing unless the aggregate state is dirty or the log replay failed. Functionally equivalent to -a.
    -v
    Verbose messaging - print details and debug statements to stdout.
    -V
    Print version information and exit (regardless of any other chosen options).
     

    EXAMPLES

    Check the 3rd partition on the 2nd hard disk, print extended information to stdout, replay the transaction log, force complete fsck.jfs checking, and give permission to repair all errors:

    fsck.jfs -v -f /dev/hdb3

    Check the 5th partition on the 1st hard disk, and report, but do not repair, any errors:

    fsck.jfs -n /dev/hda5

     

    EXIT CODE

    The exit code returned by fsck.jfs represents one of the following conditions:
     0
    No errors
     1
    File system errors corrected and/or transaction log replayed successfully
     2
    File system errors corrected, system should be rebooted if file system was mounted
     4
    File system errors left uncorrected
     8
    Operational error
     16
    Usage or syntax error
     128
    Shared library error

     

    REPORTING BUGS

    If you find a bug in JFS or fsck.jfs, please report it via the bug tracking system ("Report Bugs" section) of the JFS project web site:

    http://oss.software.ibm.com/jfs
    

    Please send as much pertinent information as possible, including the complete output of running fsck.jfs with the -v option on the JFS device.

     

    SEE ALSO

    fsck(8), mkfs.jfs(8), logdump(8), logredo(8), xchklog(8), xchkdmp(8), xpeek(8)

     

    AUTHORS

    Barry Arndt  (barndt@us.ibm.com)
    William Braswell, Jr.
    
    
    fsck.jfs is maintained by IBM.
    See the JFS project web site for more details:
    http://oss.software.ibm.com/jfs
    


     

    Index

    NAME
    SYNOPSIS
    DESCRIPTION
    WARNING
    OPTIONS
    EXAMPLES
    EXIT CODE
    REPORTING BUGS
    SEE ALSO
    AUTHORS


    Поиск по тексту MAN-ов: 




    Спонсоры:
    PostgresPro
    Inferno Solutions
    Hosting by Hoster.ru
    Хостинг:

    Закладки на сайте
    Проследить за страницей
    Created 1996-2022 by Maxim Chirkov
    Добавить, Поддержать, Вебмастеру