| 1 |
.TH xfs_logprint 8 |
| 2 |
.SH NAME |
| 3 |
xfs_logprint \- print the log of an XFS filesystem |
| 4 |
.SH SYNOPSIS |
| 5 |
.B xfs_logprint |
| 6 |
[ |
| 7 |
.I options |
| 8 |
] |
| 9 |
.I device |
| 10 |
.SH DESCRIPTION |
| 11 |
.B xfs_logprint |
| 12 |
prints the log of an XFS filesystem (see |
| 13 |
.BR xfs (5)). |
| 14 |
The |
| 15 |
.I device |
| 16 |
argument is the pathname of the partition or logical volume |
| 17 |
containing the filesystem. The |
| 18 |
.I device |
| 19 |
can be a regular file if the |
| 20 |
.B \-f |
| 21 |
option is used. The contents of the filesystem remain undisturbed. |
| 22 |
There are two major modes of operation in |
| 23 |
.BR xfs_logprint . |
| 24 |
.PP |
| 25 |
One mode is better for filesystem operation debugging. |
| 26 |
It is called the transactional view and is enabled through the |
| 27 |
.B \-t |
| 28 |
option. The transactional view prints only the portion of the log that |
| 29 |
pertains to recovery. In other words, it prints out complete transactions |
| 30 |
between the tail and the head. This view tries to display each transaction |
| 31 |
without regard to how they are split across log records. |
| 32 |
.PP |
| 33 |
The second mode starts printing out information from the beginning of the log. |
| 34 |
Some error blocks might print out in the beginning because the last log |
| 35 |
record usually overlaps the oldest log record. A message is |
| 36 |
printed when the physical end of the log is reached and when the |
| 37 |
logical end of the log is reached. A log record view is displayed |
| 38 |
one record at a time. Transactions that span log records may not be |
| 39 |
decoded fully. |
| 40 |
.SH OPTIONS |
| 41 |
.TP |
| 42 |
.B \-b |
| 43 |
Extract and print buffer information. Only used in transactional view. |
| 44 |
.TP |
| 45 |
.B \-c |
| 46 |
Attempt to continue when an error is detected. |
| 47 |
.TP |
| 48 |
.BI \-C " filename" |
| 49 |
Copy the log from the filesystem to the file |
| 50 |
.IR filename . |
| 51 |
The log itself is not printed. |
| 52 |
.TP |
| 53 |
.B \-d |
| 54 |
Dump the log from front to end, printing where each log record is located |
| 55 |
on disk. |
| 56 |
.TP |
| 57 |
.B \-D |
| 58 |
Do not decode anything; just print data. |
| 59 |
.TP |
| 60 |
.B \-e |
| 61 |
Exit when an error is found in the log. Normally, |
| 62 |
.B xfs_logprint |
| 63 |
tries to continue and unwind from bad logs. |
| 64 |
However, sometimes it just dies in bad ways. |
| 65 |
Using this option prevents core dumps. |
| 66 |
.TP |
| 67 |
.B \-f |
| 68 |
Specifies that the filesystem image to be processed is stored in a |
| 69 |
regular file at |
| 70 |
.I device |
| 71 |
(see the |
| 72 |
.BR mkfs.xfs "(8) " -d |
| 73 |
.I file |
| 74 |
option). |
| 75 |
This might happen if an image copy of a filesystem has been made into |
| 76 |
an ordinary file with |
| 77 |
.BR xfs_copy (8). |
| 78 |
.TP |
| 79 |
.B \-h |
| 80 |
Print u32 hex dump data in host-endian order. |
| 81 |
The default is to print without any endian decoding. |
| 82 |
.TP |
| 83 |
.BI \-l " logdev" |
| 84 |
External log device. Only for those filesystems which use an external log. |
| 85 |
.TP |
| 86 |
.B \-i |
| 87 |
Extract and print inode information. Only used in transactional view. |
| 88 |
.TP |
| 89 |
.B \-q |
| 90 |
Extract and print quota information. Only used in transactional view. |
| 91 |
.TP |
| 92 |
.B \-n |
| 93 |
Do not try and interpret log data; just interpret log header information. |
| 94 |
.TP |
| 95 |
.B \-o |
| 96 |
Also print buffer data in hex. |
| 97 |
Normally, buffer data is just decoded, so better information can be printed. |
| 98 |
.TP |
| 99 |
.BI \-s " start-block" |
| 100 |
Override any notion of where to start printing. |
| 101 |
.TP |
| 102 |
.B \-t |
| 103 |
Print out the transactional view. |
| 104 |
.TP |
| 105 |
.B \-v |
| 106 |
Print "overwrite" data. |
| 107 |
.TP |
| 108 |
.B \-V |
| 109 |
Prints the version number and exits. |
| 110 |
.SH SEE ALSO |
| 111 |
.BR mkfs.xfs (8), |
| 112 |
.BR mount (8). |