Cluster fs resource always executes an fsck when it is started, even if force_fsck="no" in RHEL 5 or 6
Issue
- When my cluster service with an fs resource is starting or recovering, it always runs an
fsck
- An
fs
resource always has an fsck run during startup even ifforce_fsck
is unset, or is set tono
- In a two node cluster environment, an ext3 file system is used by both nodes. When this file system is migrated to the other node, the other node take the file system an
fsck
on the file system is run. On a big file system this take a lot of time.
Environment
- Red Hat Enterprise Linux (RHEL) 5 or 6 with the High Availability Add On
- One or more
fs
resources in a service/etc/cluster/cluster.conf
- The
fstype
attribute on thefs
resource is not set, or is set to an invalid value
- The
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.