From: Abdul Haleem <abdhalee@linux.vnet.ibm.com>
To: linux-xfs@vger.kernel.org
Cc: linuxppc-dev@lists.ozlabs.org, sachinp@linux.vnet.ibm.com,
mpe@ellerman.id, aneesh.kumar@linux.vnet.ibm.com
Subject: [PowerPC] XFS : Metadata corruption detected at 0x60000000382100b0, xfs_agf block
Date: Fri, 03 Mar 2017 14:34:10 +0530 [thread overview]
Message-ID: <1488531850.5962.22.camel@abdul-ThinkPad-T450> (raw)
Hi,
Reboot fails for PowerPC machine running RHEL7.3 (3.10.0-514.el7)
following these messages:
SGI XFS with ACLs, security attributes, no debug enabled
XFS (dm-0): Mounting V5 Filesystem
FS (dm-0): Starting recovery (logdev: internal)
XFS (dm-0): Metadata corruption detected at 0x60000000382100b0, xfs_agf
block 0x4b00001
XFS (dm-0): Unmount and run xfs_repair
XFS (dm-0): First 64 bytes of corrupted metadata buffer:
c0000000f06b7200: 58 41 47 46 00 00 00 01 00 00 00 03 00 32 00 00
XAGF.........2..
c0000000f06b7210: 00 00 00 01 00 00 00 02 00 00 00 00 00 00 00
01 ................
c0000000f06b7220: 00 00 00 01 00 00 00 00 00 00 00 76 00 00 00
02 ...........v....
c0000000f06b7230: 00 00 00 04 00 2d 0c c7 00 2a 14 62 00 00 00
00 .....-...*.b....
XFS (dm-0): metadata I/O error: block 0x4b00001
("xfs_trans_read_buf_map") error 117 numblks 1
Failed to mount /sysroot.
Steps to recreate:
Run some file system test (ltp or xfs/086) on 4.10.0 upstream kernel
built on the PowerVM LPAR after the test completes, reboot the machine
back to base kernel, boot falls to dracut mode with above messages,
every time it requires a xfs_repair to recover the file system.
--
Regard's
Abdul Haleem
IBM Linux Technology Centre
next reply other threads:[~2017-03-03 14:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-03 9:04 Abdul Haleem [this message]
2017-03-03 11:59 ` [PowerPC] XFS : Metadata corruption detected at 0x60000000382100b0, xfs_agf block Michael Ellerman
2017-03-07 20:44 ` Eric Sandeen
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=1488531850.5962.22.camel@abdul-ThinkPad-T450 \
--to=abdhalee@linux.vnet.ibm.com \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=linux-xfs@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id \
--cc=sachinp@linux.vnet.ibm.com \
/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