{"id":3779,"date":"2022-12-20T17:20:03","date_gmt":"2022-12-20T20:20:03","guid":{"rendered":"http:\/\/lode.uno\/linux-man\/index.php\/2022\/12\/20\/jfs_fsck-man8-2\/"},"modified":"2022-12-20T17:20:03","modified_gmt":"2022-12-20T20:20:03","slug":"jfs_fsck-man8-2","status":"publish","type":"post","link":"https:\/\/lode.uno\/linux-man\/2022\/12\/20\/jfs_fsck-man8-2\/","title":{"rendered":"jfs_fsck (man8)"},"content":{"rendered":"

jfs_fsck<\/h1>\n

NAME<\/a>
SYNOPSIS<\/a>
DESCRIPTION<\/a>
WARNING<\/a>
OPTIONS<\/a>
EXAMPLES<\/a>
EXIT CODE<\/a>
REPORTING BUGS<\/a>
SEE ALSO<\/a>
AUTHORS<\/a> <\/p>\n

\n

NAME <\/a> <\/h2>\n

jfs_fsck<\/b> \u2212 initiate replay of the JFS transaction log, and check and repair a JFS formatted device<\/p>\n

SYNOPSIS <\/a> <\/h2>\n

jfs_fsck<\/b> [ -afnpvV<\/b> ] [ -j<\/b> journal_device<\/i> ] [ –omit_journal_replay<\/b> ] [ –replay_journal_only<\/b> ] device<\/i><\/p>\n

DESCRIPTION <\/a> <\/h2>\n

jfs_fsck<\/b><\/i> is used to replay the JFS transaction log, check a JFS formatted device for errors, and fix any errors found.<\/p>\n

device<\/i> is the special file name corresponding to the actual device to be checked (e.g. \/dev\/hdb1<\/b>).<\/p>\n

jfs_fsck<\/b> must be run as root.<\/p>\n

WARNING <\/a> <\/h2>\n

jfs_fsck<\/b> should only be used to check an unmounted<\/b> file system or a file system that is mounted READ ONLY. Using jfs_fsck<\/b> to check a file system mounted other than READ ONLY could seriously damage the file system!<\/p>\n

OPTIONS <\/a> <\/h2>\n

If no options are selected, the default is \u2212p<\/b>.<\/p>\n\n\n\n
<\/td>\n\n

\u2212a<\/b><\/p>\n<\/td>\n

<\/td>\n\n

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 \u2212p<\/b>. Autocheck mode is typically the default mode used when jfs_fsck<\/b> is called at boot time.<\/p>\n<\/td>\n<\/tr>\n

<\/td>\n\n

\u2212f<\/b><\/p>\n<\/td>\n

<\/td>\n\n

Replay the transaction log and force checking even if the file system appears clean. Repair all problems automatically.<\/p>\n<\/td>\n<\/tr>\n<\/table>\n

\u2212j<\/b> journal_device<\/i><\/p>\n

Specify the journal device.<\/p>\n\n\n
<\/td>\n\n

\u2212n<\/b><\/p>\n<\/td>\n

<\/td>\n\n

Open the file system read only. Do not replay the transaction log. Report errors, but do not repair them.<\/p>\n<\/td>\n<\/tr>\n<\/table>\n

\u2212-omit_journal_replay<\/b><\/p>\n

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>\n\n\n
<\/td>\n\n

\u2212p<\/b><\/p>\n<\/td>\n

<\/td>\n\n

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 \u2212a<\/b>.<\/p>\n<\/td>\n<\/tr>\n<\/table>\n

\u2212-replay_journal_only<\/b><\/p>\n

Only replay the transaction log. Do not continue with a full file system check if the replay fails or if the file system is still dirty even after a journal replay. In general, this option should only be used for debugging purposes as it could leave the file system in an unmountable state. This option cannot be used with -f<\/b>, -n<\/b>, or –omit_journal_replay<\/b>.<\/p>\n\n\n\n
<\/td>\n\n

\u2212v<\/b><\/p>\n<\/td>\n

<\/td>\n\n

Verbose messaging – print details and debug statements to stdout.<\/p>\n<\/td>\n<\/tr>\n

<\/td>\n\n

\u2212V<\/b><\/p>\n<\/td>\n

<\/td>\n\n

Print version information and exit (regardless of any other chosen options).<\/p>\n<\/td>\n<\/tr>\n<\/table>\n

EXAMPLES <\/a> <\/h2>\n

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:<\/p>\n

jfs_fsck \u2212v \u2212f \/dev\/hdb3<\/b><\/p>\n

Check the 5th partition on the 1st hard disk, and report, but do not repair, any errors:<\/p>\n

jfs_fsck \u2212n \/dev\/hda5<\/b><\/p>\n

EXIT CODE <\/a> <\/h2>\n

The exit code returned by jfs_fsck<\/b> represents one of the following conditions:<\/p>\n\n\n\n\n\n\n\n\n
<\/td>\n\n

\u00a0 0<\/b><\/p>\n<\/td>\n

<\/td>\n\n

No errors<\/p>\n<\/td>\n<\/tr>\n

<\/td>\n\n

\u00a0 1<\/b><\/p>\n<\/td>\n

<\/td>\n\n

File system errors corrected and\/or transaction log replayed successfully<\/p>\n<\/td>\n<\/tr>\n

<\/td>\n\n

\u00a0 2<\/b><\/p>\n<\/td>\n

<\/td>\n\n

File system errors corrected, system should be rebooted if file system was mounted<\/p>\n<\/td>\n<\/tr>\n

<\/td>\n\n

\u00a0 4<\/b><\/p>\n<\/td>\n

<\/td>\n\n

File system errors left uncorrected<\/p>\n<\/td>\n<\/tr>\n

<\/td>\n\n

\u00a0 8<\/b><\/p>\n<\/td>\n

<\/td>\n\n

Operational error<\/p>\n<\/td>\n<\/tr>\n

<\/td>\n\n

\u00a0 16<\/b><\/p>\n<\/td>\n

<\/td>\n\n

Usage or syntax error<\/p>\n<\/td>\n<\/tr>\n

<\/td>\n\n

\u00a0 128<\/b><\/p>\n<\/td>\n

<\/td>\n\n

Shared library error<\/p>\n<\/td>\n<\/tr>\n<\/table>\n

REPORTING BUGS <\/a> <\/h2>\n

If you find a bug in JFS<\/b> or jfs_fsck<\/b>, please report it via the bug tracking system (“Report Bugs” section) of the JFS project web site:
http:\/\/jfs.sourceforge.net\/<\/p>\n

Please send as much pertinent information as possible, including the complete output of running jfs_fsck<\/b> with the \u2212v<\/b> option on the JFS device.<\/p>\n

SEE ALSO <\/a> <\/h2>\n

fsck<\/b>(8), jfs_mkfs<\/b>(8), jfs_fscklog<\/b>(8), jfs_tune<\/b>(8), jfs_logdump<\/b>(8), jfs_debugfs<\/b>(8)<\/p>\n

AUTHORS <\/a> <\/h2>\n

Barry Arndt (barndt@us.ibm.com)
William Braswell, Jr.<\/p>\n

jfs_fsck<\/b> is maintained by IBM.
See the JFS project web site for more details:
http:\/\/jfs.sourceforge.net\/<\/p>\n

\n","protected":false},"excerpt":{"rendered":"

jfs_fsck \u2212 initiate replay of the JFS transaction log, and check and repair a JFS formatted device <\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[2],"tags":[5,52,31,4],"class_list":["post-3779","post","type-post","status-publish","format-standard","hentry","category-8-administracion-del-sistema","tag-5","tag-administracion","tag-fsck","tag-man8"],"gutentor_comment":0,"_links":{"self":[{"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/posts\/3779","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/comments?post=3779"}],"version-history":[{"count":0,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/posts\/3779\/revisions"}],"wp:attachment":[{"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/media?parent=3779"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/categories?post=3779"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/tags?post=3779"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}