logredo(8) [redhat man page]

logredo(8)						 JFS utility - replay journal log						logredo(8)

NAME

       logredo - "replay" a JFS formatted device's journal log

SYNOPSIS

       logredo device

DESCRIPTION

       logredo	applies  all committed transactions recorded in the JFS journal log since the most recent synch point.	Its goal is to put the JFS
       file system in the state it would have been in if all transactions had been applied, in order, by the JFS file system itself.

       device is the special file name corresponding to the actual device on which the journal log will be replayed (e.g.  /dev/hdb1 ).

       logredo must be run as root.

WARNING

       logredo is called from within fsck.jfs, and is not recommended to be run as a stand-alone utility unless completely necessary, and only	by
       advanced users with a clear understanding of journaling in a file system.

BUGS

       If you find a bug in JFS or logredo, 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 any logredo error messages and the complete output of running fsck.jfs
       with the -v option on the JFS device.

SEE ALSO

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

AUTHORS

       Barry Arndt  (barndt@us.ibm.com)
       William Braswell, Jr.

       logredo is maintained by IBM.
       See the JFS project web site for more details:
       http://oss.software.ibm.com/jfs

								 October 10, 2001							logredo(8)

xchklog(8)						JFS utility - extract fsck.jfs log						xchklog(8)

NAME

       xchklog - extract a log from the JFS fsck workspace into a file

SYNOPSIS

       xchklog [ -f output.file ] [ -p ] [ -V ] device

DESCRIPTION

       xchklog extracts the contents of either the most recent or immediately prior JFS fsck service log from the specified device, and writes the
       output into a specified or default file.  (The default file name is <pwd>fscklog.new.  If the -p option is used, the default file  name	is
       <pwd>fscklog.old.)

       The contents of the output file can be formatted into text by using the JFS utility xchkdmp.

       device is the special file name corresponding to the actual device from which the fsck log will be extracted (e.g.  /dev/hdb1 ).

OPTIONS

       -f output.file
	      Specify the output file name, overriding the default file name.

	      output.file must be 127 characters or less in length.

	      output.file will be created in the present working directory unless it is fully qualified.

       -p     Extract the prior log (as opposed to the most recent log).

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

EXAMPLES

	Extract the most recent log on /dev/hda5 into <pwd>fscklog.new:

	      xchklog /dev/hda5

       Extract the most recent log on /dev/hdb3 into /temp/l9651107.log:

	      xchklog -f /temp/l9651107.log /dev/hdb3

       Extract the prior log on /dev/hdb4 into <pwd>fscklog.old:

	      xchklog -p /dev/hdb4

REPORTING BUGS

       If you find a bug in JFS or xchklog, 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 any xchklog error messages and the complete output of running fsck.jfs
       with the -v option on the JFS device.

SEE ALSO

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

AUTHOR

       Barry Arndt  (barndt@us.ibm.com)

       xchklog is maintained by IBM.
       See the JFS project web site for more details:
       http://oss.software.ibm.com/jfs

								 January 11, 2002							xchklog(8)