Why mtime and ctime information does get propagated across the nodes with gfs2 filesystem in RHEL6 cluster?

Solution Unverified - Updated -

Issue

  • Whenever the contents of a file on a GFS2 file system changes without changing the size, the date stamp does not propagate, and the file has the same (correct) contents on all cluster members.
  • If the file size is changed by writing more records into it, the date stamp does propagate properly across the nodes.
  • Why does it happen?

Environment

  • Red Hat Enterprise Linux Server 6.3 (with the High Availability and Resilient Storage Add Ons)
  • A Global Filesystem 2(GFS2)

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.