XFS corruption detected in xfs_btree_check_sblock() function.

Solution Verified - Updated -

Issue

The XFS filesystem went to read-only mode with following call-trace in messages:

Aug  1 04:41:07 localhost kernel: ffff88013b803000: 49 4e 81 80 02 02 00 00 00 00 00 64 00 00 00 64  IN.........d...d
Aug  1 04:41:07 localhost kernel: XFS (sdd1): Internal error xfs_btree_check_sblock at line 120 of file fs/xfs/xfs_btree.c.  Caller 0xffffffffa023e874
Aug  1 04:41:07 localhost kernel: 
Aug  1 04:41:07 localhost kernel: Pid: 30586, comm: postgres Not tainted 2.6.32-431.el6.x86_64 #1
Aug  1 04:41:07 localhost kernel: Call Trace:
Aug  1 04:41:07 localhost kernel: [<ffffffffa0251e5f>] ? xfs_error_report+0x3f/0x50 [xfs]
Aug  1 04:41:07 localhost kernel: [<ffffffffa023e874>] ? xfs_btree_check_block+0x14/0x30 [xfs]
Aug  1 04:41:07 localhost kernel: [<ffffffffa0251ece>] ? xfs_corruption_error+0x5e/0x90 [xfs]
Aug  1 04:41:07 localhost kernel: [<ffffffffa023e874>] ? xfs_btree_check_block+0x14/0x30 [xfs]
Aug  1 04:41:07 localhost kernel: [<ffffffffa023e7be>] ? xfs_btree_check_sblock+0xbe/0x160 [xfs]

Environment

  • Red Hat Enterprise Linux 6.5

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.