From: bugzilla-daemon@bugzilla.kernel.org
To: linux-xfs@vger.kernel.org
Subject: [Bug 201823] inconsistent behaviour of xfs_db, xfs_repair and xfs_scrub
Date: Mon, 03 Dec 2018 21:21:59 +0000 [thread overview]
Message-ID: <bug-201823-201763-ooJ0pkI51a@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-201823-201763@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=201823
--- Comment #7 from Eric Sandeen (sandeen@sandeen.net) ---
So, the frag command emits these warnings under a debug build:
# xfs_db -c frag -r /dev/sde1
bad inode magic/vsn daddr 8366784 #0 (magic=5844)
Metadata corruption detected at 0x4289c3, xfs_inode block 0x7faac0/0x8000
bad inode magic/vsn daddr 34386688 #0 (magic=0)
Metadata corruption detected at 0x4289c3, xfs_inode block 0x20cb300/0x8000
bad inode magic/vsn daddr 36967232 #0 (magic=0)
Metadata corruption detected at 0x4289c3, xfs_inode block 0x2341340/0x8000
If we look at each of those blocks (daddr) after a blockget -n,
xfs_db> daddr 8366784
xfs_db> blockuse
block 1045848 (0/1045848) type dir inode 8366719
xfs_db> daddr 34386688
xfs_db> blockuse
block 5292640 (1/1098336) type free2
xfs_db> daddr 36967232
xfs_db> blockuse
block 5615208 (1/1420904) type data inode 44934228
The "inode" corruption it's finding isn't actually in inode blocks...
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2018-12-03 21:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-01 8:16 [Bug 201823] New: inconsistent behaviour of xfs_db, xfs_repair and xfs_scrub bugzilla-daemon
2018-12-01 19:13 ` [Bug 201823] " bugzilla-daemon
2018-12-01 22:44 ` [Bug 201823] New: " Dave Chinner
2018-12-01 22:44 ` [Bug 201823] " bugzilla-daemon
2018-12-02 1:14 ` bugzilla-daemon
2018-12-02 8:27 ` bugzilla-daemon
2018-12-02 17:02 ` bugzilla-daemon
2018-12-02 17:28 ` Matthias Bodenbinder
2018-12-02 17:40 ` bugzilla-daemon
2018-12-03 21:21 ` bugzilla-daemon [this message]
2018-12-03 22:16 ` bugzilla-daemon
2018-12-03 22:35 ` bugzilla-daemon
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=bug-201823-201763-ooJ0pkI51a@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.