[PATCH 06/37] debugfs: force logdump to display (old) journal contents

Darrick J. Wong
2014-05-01T23:13:07Z

If the user passes -a more than once to logdump, try to dump old log
contents. This can be used to try to track down journal problems even
after recovery.

Signed-off-by: Darrick J. Wong <darrick.wong@oracle.com>
---
debugfs/logdump.c | 11 ++++++++---
1 file changed, 8 insertions(+), 3 deletions(-)

diff --git a/debugfs/logdump.c b/debugfs/logdump.c
index 8b9dc5b..bf4bef5 100644
--- a/debugfs/logdump.c
+++ b/debugfs/logdump.c
@@ -393,9 +393,13 @@ static void dump_journal(char *cmdname, FILE *out_file,
fprintf(out_file, "Journal starts at block %u, transaction %u\n",
blocknr, transaction);

- if (!blocknr)
+ if (!blocknr) {
/* Empty journal, nothing to do. */
- return;
+ if (dump_all < 2)
+ return;
+ else
+ blocknr = 1;
+ }

while (1) {
retval = read_journal_block(cmdname, source,
@@ -420,7 +424,8 @@ static void dump_journal(char *cmdname, FILE *out_file,
fprintf (out_file, "Found sequence %u (not %u) at "
"block %u: end of journal.\n",
sequence, transaction, blocknr);
- return;
+ if (dump_all < 2)
+ return;
}

if (dump_descriptors) {