From: Donald Douwsma <ddouwsma@redhat.com>
To: linux-xfs@vger.kernel.org
Cc: Donald Douwsma <ddouwsma@redhat.com>
Subject: [PATCH 0/2] xfsprogs: xfs_logprint misc log decoding issues
Date: Thu, 28 Jan 2021 18:37:06 +1100 [thread overview]
Message-ID: <20210128073708.25572-1-ddouwsma@redhat.com> (raw)
I've been seeing confusing superblock transactions in logprint, this is
an attempt to resolve them and make debugging misc buffer updates easier.
Before
$ xfs_logprint -o xfs.image
----------------------------------------------------------------------------
Oper (2): tid: c32589f8 len: 24 clientid: TRANS flags: none
BUF: #regs: 2 start blkno: 0 (0x0) len: 1 bmap size: 1 flags: 0x9000
Oper (3): tid: c32589f8 len: 384 clientid: TRANS flags: none
SUPER BLOCK Buffer:
icount: 6360863066640355328 ifree: 262144 fdblks: 0 frext: 0
----------------------------------------------------------------------------
After
$ xfs_logprint -o xfs.image
----------------------------------------------------------------------------
Oper (2): tid: c32589f8 len: 24 clientid: TRANS flags: none
BUF: #regs: 2 start blkno: 0 (0x0) len: 1 bmap size: 1 flags: 0x9000
Oper (3): tid: c32589f8 len: 384 clientid: TRANS flags: none
SUPER BLOCK Buffer:
icount: 64 ifree: 61 fdblks: 259564 frext: 0
0 42534658 100000 0 400 0 0 0 0
8 84a2ced5 974f8da4 8fd4b0b3 9a870a19 0 4000200 0 80000000
10 0 81000000 0 82000000 1000000 100 4000000 0
18 a0000 2a4b4 10000001 0 0 0 408090c 19000010
20 0 40000000 0 3d000000 0 ecf50300 0 0
28 ffffffff ffffffff ffffffff ffffffff 0 2000000 0 0
30 0 1000000 8a020000 8a020000 0 0 0 0
38 0 0 0 0 0 0 0 0
40 0 0 0 0 0 0 0 0
48 0 0 0 0 0 0 0 0
50 0 0 0 0 0 0 0 0
58 0 0 0 0 0 0 0 0
----------------------------------------------------------------------------
Donald Douwsma (2):
xfs_logprint: print misc buffers when using -o
xfs_logprint: decode superblock updates correctly
logprint/log_misc.c | 41 ++++++++++++----------------------------
logprint/log_print_all.c | 25 +++++++++++-------------
2 files changed, 23 insertions(+), 43 deletions(-)
--
2.27.0
next reply other threads:[~2021-01-28 7:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-28 7:37 Donald Douwsma [this message]
2021-01-28 7:37 ` [PATCH 1/2] xfs_logprint: print misc buffers when using -o Donald Douwsma
2021-01-28 17:35 ` Darrick J. Wong
2021-01-28 21:51 ` Donald Douwsma
2021-01-28 7:37 ` [PATCH 2/2] xfs_logprint: decode superblock updates correctly Donald Douwsma
2021-01-28 17:28 ` Darrick J. Wong
2021-01-28 21:59 ` Donald Douwsma
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210128073708.25572-1-ddouwsma@redhat.com \
--to=ddouwsma@redhat.com \
--cc=linux-xfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox