Getting ext/xfs filesystem corruption after 'pvmove'

Solution Verified - Updated -

Issue

  • We have an Active/Passive cluster and the lvm volume/filesystems are mounted on active node only. Due to the storage migration requirements, the LVM PV were moved from old storage to a new storage using pvmove command from passive node. But after this migration, the filesystems got corrupt:

    XFS (dm-210): Corruption detected! Free inode 0x121c4e0 not marked free! (mode 0x81a0)
XFS (dm-210): Internal error xfs_trans_cancel at line 984 of file fs/xfs/xfs_trans.c.  Caller xfs_create+0x46f/0x6a0 [xfs]
[...]

kernel: EXT4-fs error (device dm-10): ext4_journal_start_sb: Detected aborted journal
kernel: EXT4-fs (dm-10): Remounting filesystem read-only
[...]

Environment

  • Red Hat Enterprise Linux (All versions)
  • ext2/ext3/ext4 or XFS filesystem
  • Any Active/Passive cluster software

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