{"id":2794,"date":"2022-12-20T15:17:19","date_gmt":"2022-12-20T18:17:19","guid":{"rendered":"http:\/\/lode.uno\/linux-man\/index.php\/2022\/12\/20\/jfs_fscklog-man8\/"},"modified":"2022-12-20T15:17:19","modified_gmt":"2022-12-20T18:17:19","slug":"jfs_fscklog-man8","status":"publish","type":"post","link":"https:\/\/lode.uno\/linux-man\/2022\/12\/20\/jfs_fscklog-man8\/","title":{"rendered":"jfs_fscklog (man8)"},"content":{"rendered":"

jfs_fscklog<\/h1>\n

NAME<\/a>
SYNOPSIS<\/a>
DESCRIPTION<\/a>
OPTIONS<\/a>
EXAMPLES<\/a>
REPORTING BUGS<\/a>
SEE ALSO<\/a>
AUTHOR<\/a> <\/p>\n

\n

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

jfs_fscklog<\/b> \u2212 extract a JFS fsck service log into a file and\/or format and display the extracted file<\/p>\n

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

jfs_fscklog<\/b> [ -d<\/b> ] [ -e<\/b> device<\/i> ] [ -f<\/b> output.file<\/i> ] [ -p<\/b> ] [ -V<\/b> ]<\/p>\n

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

jfs_fscklog<\/b> with option -e<\/b> device<\/i> extracts the contents of either the most recent or immediately prior (specified with option -p<\/b>) JFS fsck service log from the specified device, and writes the output to a file. The file name may be specified with the -f<\/b> option, or the default file name is fscklog.new<\/i>. If the -p<\/b> option is used, the default file name is fscklog.old<\/i>.<\/p>\n

jfs_fscklog<\/b> with option -d<\/b> formats and displays the contents of the extracted file.<\/p>\n

jfs_fscklog<\/b> with options -d<\/b> and -e<\/b> device<\/i> extracts and displays the JFS fsck service log.<\/p>\n

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

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

<\/td>\n\n

Format and display a previously extracted JFS fsck service log.<\/p>\n<\/td>\n<\/tr>\n<\/table>\n

\u2212e<\/b> device<\/i><\/p>\n

Extract the JFS fsck service log from device<\/i> and store it in a file. (device<\/i> is the special file name corresponding to the actual device from which the fsck log will be extracted (e.g. \/dev\/hdb1<\/b> )).<\/p>\n

\u2212f<\/b> file.name<\/i><\/p>\n

Specify the file name, overriding the default file name. When used with -e<\/b> device<\/i>, file.name specifies the name of the file into which the JFS fsck log will be extracted. When used with -d<\/b>, file.name specifies the name of the extracted file whose contents will be formatted and displayed.<\/p>\n

file.name<\/i> must be 127 characters or less in length.<\/p>\n

file.name<\/i> will be created in the present working directory unless it is fully qualified.<\/p>\n\n\n\n
<\/td>\n\n

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

<\/td>\n\n

Extract the prior log (as opposed to the most recent log).<\/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

Extract the most recent JFS fsck log on \/dev\/hda5 into fscklog.new<\/i>:<\/p>\n

jfs_fscklog -e \/dev\/hda5<\/b><\/p>\n

Extract the most recent JFS fsck log on \/dev\/hdb3 into \/temp\/l9651107.log<\/i>:<\/p>\n

jfs_fscklog -e \/dev\/hdb3 -f \/temp\/l9651107.log<\/b><\/p>\n

Display the JFS fsck log that was extracted into \/temp\/l9651107.log<\/i>:<\/p>\n

jfs_fscklog -d -f \/temp\/l9651107.log<\/b><\/p>\n

Extract and display the previous JFS fsck log from \/dev\/hda8:<\/p>\n

jfs_fscklog -e \/dev\/hda8 -d -p<\/b><\/p>\n

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

If you find a bug in JFS<\/b> or jfs_fscklog,<\/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 any jfs_fscklog<\/b> error messages and the complete output of running jfs_fsck<\/b> with the \u2212v<\/b> option on the JFS device.<\/p>\n

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

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

AUTHOR <\/a> <\/h2>\n

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

jfs_fscklog<\/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_fscklog \u2212 extract a JFS fsck service log into a file and\/or format and display the extracted file <\/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,148,4],"class_list":["post-2794","post","type-post","status-publish","format-standard","hentry","category-8-administracion-del-sistema","tag-5","tag-administracion","tag-jfs_fscklog","tag-man8"],"gutentor_comment":0,"_links":{"self":[{"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/posts\/2794","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=2794"}],"version-history":[{"count":0,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/posts\/2794\/revisions"}],"wp:attachment":[{"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/media?parent=2794"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/categories?post=2794"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/tags?post=2794"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}