Bug 1333142

Summary: Provide way to determine if xlator option 'resync-failed-syncs-after-fsync' is supported
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: Jeff Cody <jcody>
Component: write-behindAssignee: Csaba Henk <csaba>
Status: CLOSED WONTFIX QA Contact: Rahul Hinduja <rhinduja>
Severity: medium Docs Contact:
Priority: high    
Version: unspecifiedCC: atumball, rhs-bugs, sheggodu
Target Milestone: ---Keywords: FutureFeature, Triaged, ZStream
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-04-16 18:18:23 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1333358    
Bug Blocks:    

Description Jeff Cody 2016-05-04 18:41:08 UTC 
In the current upstream Gluster, the write-behind cache supports a xlator option 'resync-failed-syncs-after-fsync', which has Gluster retain the cache on fsync failure, until the file descriptor is flushed/closed.  With this QEMU, when using the libglusterfs library, can perform retries on a fsync failure.

However, QEMU has no way of determining at runtime if this xlator option is supported.  The api glfs_set_xlator_option() will return success even for unknown options.  It would be very useful for us to be able to determine if we can use the new xlator option - until we can determine if it is support, QEMU must act as if it is not supported.
Comment 4 Csaba Henk 2018-03-05 13:41:44 UTC 
This will be addressed by upstream enhancement https://github.com/gluster/glusterfs/issues/263 in a more general context.