Welcome to Linux Knowledge Base and Tutorial
"The place where you learn linux"
GetNetWise: You
e One Click Away

 Create an AccountHome | Submit News | Your Account  

Tutorial Menu
Linux Tutorial Home
Table of Contents

· Introduction to Operating Systems
· Linux Basics
· Working with the System
· Shells and Utilities
· Editing Files
· Basic Administration
· The Operating System
· The X Windowing System
· The Computer Itself
· Networking
· System Monitoring
· Solving Problems
· Security
· Installing and Upgrading
· Linux and Windows

Man Pages
Linux Topics
Test Your Knowledge

Site Menu
Site Map
Copyright Info
Terms of Use
Privacy Info
Masthead / Impressum
Your Account

Private Messages

News Archive
Submit News
User Articles
Web Links


The Web

Who's Online
There are currently, 61 guest(s) and 0 member(s) that are online.

You are an Anonymous user. You can register for free by clicking here




       jfs_fsck [ -afnpvV ] [ -j journal_device ] [  --omit_jour­
       nal_replay ] [ --replay_journal_only ] device


       jfs_fsck  is used to replay the JFS transaction log, check
       a JFS formatted device for  errors,  and  fix  any  errors

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

       jfs_fsck must be run as root.


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


       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.  Function­
              ally equivalent to -p.  Autocheck mode is typically
              the  default  mode  used when jfs_fsck is called at
              boot time.

       -f     Replay the transaction log and force checking  even
              if the file system appears clean.  Repair all prob­
              lems automatically.

       -j journal_device
              Specify the journal device.

       -n     Open the file system read only.  Do not replay  the
              transaction  log.  Report errors, but do not repair

              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).


       -v     Verbose messaging - print details and debug  state­
              ments to stdout.

       -V     Print  version  information and exit (regardless of
              any other chosen options).


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

              jfs_fsck -v -f /dev/hdb3

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

              jfs_fsck -n /dev/hda5


       The exit code returned by jfs_fsck 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


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

       Please  send  as  much  pertinent information as possible,
       See the JFS project web site for more details:

                         October 29, 2002             jfs_fsck(8)
Show your Support for the Linux Tutorial

Purchase one of the products from our new online shop. For each product you purchase, the Linux Tutorial gets a portion of the proceeds to help keep us going.



Security Code
Security Code
Type Security Code

Don't have an account yet? You can create one. As a registered user you have some advantages like theme manager, comments configuration and post comments with your name.

Help if you can!

Amazon Wish List

Did You Know?
The Linux Tutorial can use your help.


Tell a Friend About Us

Bookmark and Share

Web site powered by PHP-Nuke

Is this information useful? At the very least you can help by spreading the word to your favorite newsgroups, mailing lists and forums.
All logos and trademarks in this site are property of their respective owner. The comments are property of their posters. Articles are the property of their respective owners. Unless otherwise stated in the body of the article, article content (C) 1994-2013 by James Mohr. All rights reserved. The stylized page/paper, as well as the terms "The Linux Tutorial", "The Linux Server Tutorial", "The Linux Knowledge Base and Tutorial" and "The place where you learn Linux" are service marks of James Mohr. All rights reserved.
The Linux Knowledge Base and Tutorial may contain links to sites on the Internet, which are owned and operated by third parties. The Linux Tutorial is not responsible for the content of any such third-party site. By viewing/utilizing this web site, you have agreed to our disclaimer, terms of use and privacy policy. Use of automated download software ("harvesters") such as wget, httrack, etc. causes the site to quickly exceed its bandwidth limitation and are therefore expressly prohibited. For more details on this, take a look here

PHP-Nuke Copyright © 2004 by Francisco Burzi. This is free software, and you may redistribute it under the GPL. PHP-Nuke comes with absolutely no warranty, for details, see the license.
Page Generation: 0.10 Seconds