Bug 1345732
Summary: | SAMBA-DHT : Crash seen while rename operations in cifs mount and windows access of share mount | |||
---|---|---|---|---|
Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | Vivek Das <vdas> | |
Component: | distribute | Assignee: | Raghavendra G <rgowdapp> | |
Status: | CLOSED ERRATA | QA Contact: | Vivek Das <vdas> | |
Severity: | high | Docs Contact: | ||
Priority: | high | |||
Version: | rhgs-3.1 | CC: | amukherj, kramdoss, nbalacha, rcyriac, rgowdapp, rhinduja, sanandpa | |
Target Milestone: | --- | Keywords: | Regression | |
Target Release: | RHGS 3.2.0 | |||
Hardware: | Unspecified | |||
OS: | Unspecified | |||
Whiteboard: | dht-fixed, dht-dropped-3.1.3-blocker, dht-3.2.0-proposed | |||
Fixed In Version: | glusterfs-3.8.4-1 | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | ||
Clone Of: | ||||
: | 1345748 (view as bug list) | Environment: | ||
Last Closed: | 2017-03-23 05:36:32 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: | 1345748, 1351522, 1366482, 1366483 |
Description
Vivek Das
2016-06-13 05:11:56 UTC
There are two issues here: 1. inode-link failure 2. crash after an inode-link is failed. 2 is a regression introduced during 3.1.3 release period. Please file a different bug to track 1 Tried reproducing the same with a fresh setup but this is not reproducible with the above mentioned steps. Regression introduced in 3.1.3 Upstream mainline : http://review.gluster.org/14707 Upstream 3.8 : http://review.gluster.org/15157 And the fix is available in rhgs-3.2.0 as part of rebase to GlusterFS 3.8.4. Verified with the Steps to Reproduce as mentioned above with the below version samba-client-4.4.6-2.el7rhgs.x86_64 glusterfs-cli-3.8.4-3.el7rhgs.x86_64 No crash was seen hence marking it as verified. 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, 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://rhn.redhat.com/errata/RHSA-2017-0486.html |