gfs2: log which portion of the journal is replayed
authorBob Peterson <rpeterso@redhat.com>
Wed, 27 Feb 2019 20:32:36 +0000 (13:32 -0700)
committerAndreas Gruenbacher <agruenba@redhat.com>
Thu, 27 Jun 2019 19:03:58 +0000 (21:03 +0200)
commit49eb776ed9d92a91d3b1a24d83755e051bce96ff
tree69ad899eb01b0baa22de3111347d5bd9d354542c
parente955537e3262de8e56f070b13817f525f472fa00
gfs2: log which portion of the journal is replayed

When a journal is replayed, gfs2 logs a message similar to:

jid=X: Replaying journal...

This patch adds the tail and block number so that the range of the
replayed block is also printed. These values will match the values
shown if the journal is dumped with gfs2_edit -p journalX. The
resulting output looks something like this:

jid=1: Replaying journal...0x28b7 to 0x2beb

This will allow us to better debug file system corruption problems.

Signed-off-by: Bob Peterson <rpeterso@redhat.com>
Signed-off-by: Andreas Gruenbacher <agruenba@redhat.com>
fs/gfs2/recovery.c