How to run fsck on ext4/xfs filesystem in a pacemaker cluster.
Issue
- How to run fsck on a cluster-managed filesystem?
- ERROR: Couldn't successfully fsck cluster filesystem for /dev/mapper/data_vg-data_lv
- Unable to start Filesystem resource in the cluster due to one of the below errors:
kernel: EXT4-fs (dm-8): warning: mounting fs with errors, running e2fsck is recommended
lrmd[1706]: notice: test_fs_start_0:22956:stderr [ /dev/mapper/data_vg-data_lv: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY. ]
Oct 2 12:01:16 fvm-rhel-8.6-171 kernel: XFS (dm-9): Corruption of in-memory data (0x8) detected at xfs_trans_cancel+0xc6/0x130 [xfs] (fs/xfs/xfs_trans.c:958). Shutting down filesystem
Oct 2 12:01:16 fvm-rhel-8.6-171 kernel: XFS (dm-9): Please unmount the filesystem and rectify the problem(s)
Oct 2 12:01:16 fvm-rhel-8.6-171 kernel: XFS (dm-9): Failed to recover intents
Oct 2 12:01:16 fvm-rhel-8.6-171 kernel: XFS (dm-9): log mount finish failed
Oct 2 12:01:16 fvm-rhel-8.6-171 Filesystem(test_fs)[3708]: ERROR: Couldn't mount device [/dev/VG01/LV01] as /clusterfs
Oct 2 12:01:16 fvm-rhel-8.6-171 pacemaker-controld[2685]: notice: test_fs_start_0@fvm-rhel-8.6-171 output [ mount: /clusterfs: mount(2) system call failed: Structure needs cleaning.\nocf-exit-reason:Couldn't mount device [/dev/VG01/LV01] as /clusterfs\n ]
Environment
- Red Hat Enterprise Linux (7 or higher) with the High Availability or Resilient Storage Add-Ons
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.