linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
* [PowerPC] XFS : Metadata corruption detected at 0x60000000382100b0, xfs_agf block
@ 2017-03-03  9:04 Abdul Haleem
  2017-03-03 11:59 ` Michael Ellerman
  2017-03-07 20:44 ` Eric Sandeen
  0 siblings, 2 replies; 3+ messages in thread
From: Abdul Haleem @ 2017-03-03  9:04 UTC (permalink / raw)
  To: linux-xfs; +Cc: linuxppc-dev, sachinp, mpe, aneesh.kumar

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

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [PowerPC] XFS : Metadata corruption detected at 0x60000000382100b0, xfs_agf block
  2017-03-03  9:04 [PowerPC] XFS : Metadata corruption detected at 0x60000000382100b0, xfs_agf block Abdul Haleem
@ 2017-03-03 11:59 ` Michael Ellerman
  2017-03-07 20:44 ` Eric Sandeen
  1 sibling, 0 replies; 3+ messages in thread
From: Michael Ellerman @ 2017-03-03 11:59 UTC (permalink / raw)
  To: Abdul Haleem, linux-xfs; +Cc: sachinp, mpe, linuxppc-dev, aneesh.kumar

Abdul Haleem <abdhalee@linux.vnet.ibm.com> writes:

> 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.

Can you work on a better repro case?

What if you mount an XFS filesystem in the guest, run the test against
it, unmount it and then remount it. Do you see the bug then? Or does it
require a reboot to trigger?

cheers

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [PowerPC] XFS : Metadata corruption detected at 0x60000000382100b0, xfs_agf block
  2017-03-03  9:04 [PowerPC] XFS : Metadata corruption detected at 0x60000000382100b0, xfs_agf block Abdul Haleem
  2017-03-03 11:59 ` Michael Ellerman
@ 2017-03-07 20:44 ` Eric Sandeen
  1 sibling, 0 replies; 3+ messages in thread
From: Eric Sandeen @ 2017-03-07 20:44 UTC (permalink / raw)
  To: Abdul Haleem, linux-xfs; +Cc: linuxppc-dev, sachinp, mpe, aneesh.kumar

On 3/3/17 3:04 AM, Abdul Haleem wrote:
> Hi,
> 
> Reboot fails for PowerPC machine running RHEL7.3 (3.10.0-514.el7)
> following these messages:

Generally it's best to report RHEL bugs to Red Hat.
 
> 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.

... though Red Hat might tell you that running upstream kernels is
out of the supported realm.

However, this probably has to do with AGF packing changes.

> c0000000f06b7200: 58 41 47 46 00 00 00 01 00 00 00 03 00 32 00 00 XAGF.........2..
                    magic       version     sequence    length
> c0000000f06b7210: 00 00 00 01 00 00 00 02 00 00 00 00 00 00 00 01  ................
                    agf roots                           agf levels
> c0000000f06b7220: 00 00 00 01 00 00 00 00 00 00 00 76 00 00 00 02  ...........v....
                                            flfirst     fllast      
> c0000000f06b7230: 00 00 00 04 00 2d 0c c7 00 2a 14 62 00 00 00 00  .....-...*.b....
                    flcount     freeblocks  longest     btreeblks

The AGF verifier does:

        if (!(agf->agf_magicnum == cpu_to_be32(XFS_AGF_MAGIC) &&
              XFS_AGF_GOOD_VERSION(be32_to_cpu(agf->agf_versionnum)) &&
              be32_to_cpu(agf->agf_freeblks) <= be32_to_cpu(agf->agf_length) &&
              be32_to_cpu(agf->agf_flfirst) < XFS_AGFL_SIZE(mp) &&
              be32_to_cpu(agf->agf_fllast) < XFS_AGFL_SIZE(mp) &&
              be32_to_cpu(agf->agf_flcount) <= XFS_AGFL_SIZE(mp)))
                return false;

where:

#define XFS_AGFL_SIZE(mp) \
        (((mp)->m_sb.sb_sectsize - \
         (xfs_sb_version_hascrc(&((mp)->m_sb)) ? \
                sizeof(struct xfs_agfl) : 0)) / \
          sizeof(xfs_agblock_t))

and "struct xfs_agfl" packing has changed between rhel7 and upstream,
due to an early bug related to nailing down that on-disk format :/

Presumably this is what xfs_repair found and fixed?

-Eric

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2017-03-07 20:51 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2017-03-03  9:04 [PowerPC] XFS : Metadata corruption detected at 0x60000000382100b0, xfs_agf block Abdul Haleem
2017-03-03 11:59 ` Michael Ellerman
2017-03-07 20:44 ` Eric Sandeen

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).