GlusterFS processes perform lgetxattr() system calls related to bit-rot detection even though it is disabled

Solution In Progress - Updated -

Issue

While doing system call traces during normal file system activity, we found calls of the form:

lgetxattr("/path/to/brick/data/.glusterfs/12/34/1234......", "trusted.bit-rot.bad-file", ... )

This is unexpected because we have not enabled bit-rot detection on the volume, and features.bitrot is set to "disable":

# gluster volume get <volname> bitrot
Option                                  Value                                   
------                                  -----                                   
features.bitrot                         disable

Is there a solution that would eliminate these lgetxattr() calls?

Environment

  • RHGS 3.1.*

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.