EXT2 filesystem reports error: ext2_xattr_get: inode 17514526: bad block 34988032

Solution Unverified - Updated -

Issue

  • User fail to access files
  • On zLinux server users intermittently can not access files.
  • Each of 3 separate instances seem to give different sets of error messages:
Oct 14 18:19:59 hostname kernel: EXT2-fs error (device dm-10): ext2_check_page: bad entry in directory #4522004: unaligned directory entry - offset=0, inode=4026531904, rec_len=170, name_len=7
Oct 14 18:19:59 hostname kernel: EXT2-fs error (device dm-10): ext2_readdir: bad page in #4522004
Sep 20 14:08:54 hostname kernel: EXT2-fs error (device dm-10): ext2_free_blocks: bit already cleared for block 2232320
Aug 30 10:31:24 hostname kernel: EXT2-fs error (device dm-10): ext2_xattr_get: inode 17514526: bad block 34988032

Environment

  • Red Hat Enterprise Linux 5
  • Seen in RHEL 5.8(kernel-2.6.18-308.8.2.el), and RHEL 5.9
  • EXT2 and EXT3 file systems
  • Filesystem does not exceed 2TB
  • RHEL virtual guest running on a zVM Virtual host
  • 10s of other zLinux servers residing on the same LPAR do not see the issue

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content