Bug 2006205
Summary: | dht_pt_getxattr does not seem to handle virtual xattrs | ||
---|---|---|---|
Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | Shwetha K Acharya <sacharya> |
Component: | distribute | Assignee: | Shwetha K Acharya <sacharya> |
Status: | CLOSED ERRATA | QA Contact: | Pranav Prakash <prprakas> |
Severity: | urgent | Docs Contact: | |
Priority: | urgent | ||
Version: | rhgs-3.5 | CC: | mhackett, moagrawa, pprakash, rcyriac, rhs-bugs, sajmoham, sheggodu, tshacked, vdas |
Target Milestone: | --- | Keywords: | ZStream |
Target Release: | RHGS 3.5.z Batch Update 6 | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | |||
Fixed In Version: | glusterfs-6.0-60 | Doc Type: | No Doc Update |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2022-01-27 14:27:11 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: | |||
Bug Blocks: | 2004767 |
Description
Shwetha K Acharya
2021-09-21 07:22:42 UTC
@Prashant, dht_pt_getxattr() which was introduced by a patch (https://github.com/gluster/glusterfs/issues/405) for perf improvements in pass-through mode (i.e. where distribute-count is 1) does not handle virtual xattrs.Later on we merged the same in downstream also. For geo-rep there is a virtual getxattr done by geo-rep on the fuse mount via DHT_SUBVOL_STATUS_KEY and it must not be sent over the network. dht_getxattr() handles it but its missing in dht_pt_getxattr(), so the geo-rep session goes faulty.The issue will be observe only while dht subvol count is 1. The bug is critical for geo-rep aspect, Can you please give your vote? Thanks, Mohit Agrawal Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (glusterfs bug fix update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2022:0315 |