Apparent filesystem corruption after a volume is grown in an active/passive fail-over environment on RHEL

Solution Verified - Updated -

Issue

  • Ext4 file system got corrupted on RHEL6
    I have expanded a volume on an active node and grown the filesystem on it. Later when attempting to mount the volume on a different node we are not able to mount the filesystem.

    mount: wrong fs type, bad option, bad superblock on /dev/mapper/vg02-lvol0,
       missing codepage or helper program, or other error
       In some cases useful info is found in syslog - try
       dmesg | tail
    $ dmesg | tail -1
    EXT4-fs (dm-248): bad geometry: block count 301465600 exceeds size of device (209715200 blocks)
    
  • File system issue after failover to passive node on RHEL5

    kernel: EXT3-fs: mounted filesystem with ordered data mode.
    kernel: attempt to access beyond end of device
    kernel: dm-11: rw=0, want=17039384, limit=10280960
    

Environment

  • Red Hat Enterprise Linux 5
  • Red Hat Enterprise Linux 6
  • An active/passive cluster configuration with a shared disk or replicated block device.

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