The commands `gfs2_edit` and `fsck.gfs2` are erroring out on node1, but succeed on node2

Solution In Progress - Updated -

Issue

  • The commands gfs2_edit and fsck.gfs2 are erroring out on node1, but succeed on node2. The errors that are occurring on node1:
# fsck.gfs2 /dev/vg1/lv1
Initializing fsck
Validating resource group index.
Level 1 resource group check: Checking if all rgrp and rindex values are good.
bad read: Invalid argument from good_on_disk:177: block 78903296 (0x4b3f800) count: 1 size: 4096 ret: 0

# gfs2_edit -p sb /dev/vg1/lv1
bad read: Invalid argument from good_on_disk:177: block 78903296 (0x4b3f800) count: 1 size: 4096 ret: 0

Environment

  • Red Hat Enterprise Linux Server 6, 7, 8 (with the High Availability Add On and Resilient Storage Add Ons)
  • A Global Filesystem 2(gfs2)

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