Bug 1273990

Summary: No files at client after change from dht only to afr
Product: [Community] GlusterFS Reporter: Joe Julian <joe>
Component: replicateAssignee: Pranith Kumar K <pkarampu>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: high Docs Contact:
Priority: high    
Version: mainlineCC: bugs, kdhananj, ksubrahm, pkarampu, ravishankar, smohan
Target Milestone: ---Keywords: Triaged
Target Release: ---   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: 3.8.0 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-08-23 07:03:10 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:

Description Joe Julian 2015-10-21 16:37:45 UTC 
Description of problem:
After adding a replica to a dht volume, directory listing is empty.

Version-Release number of selected component (if applicable):
3.7.5

How reproducible:
always

Steps to Reproduce:
1. Create a dht volume, mount it, load it with files and directories.
2. Add a brick: volume add-brick $vol replica 2 $newserver:$brick_path
3. From any client *other than* the original server, mount the volume and ls -la

Actual results:
The only thing listed is the .trashcan

Expected results:
All the files should be there.

Additional info:
This is not corrected with a heal, nor a heal full, nor stopping and starting the volume. The fuse .vol file is correct. Disabling every performance translator between replicate and fuse has no effect.

The two ways of correcting this are:
* mount the volume on the original server and ls -la the root directory
* stat *by name* all the files that should be in the volume root from any client
Comment 1 Anuradha 2016-01-14 12:40:48 UTC 
The following patches have been sent the tackle this issue :
1) http://review.gluster.org/12451
2) http://review.gluster.org/12454

Moving the state to POST.
Comment 2 Mike McCune 2016-03-28 22:17:27 UTC 
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions
Comment 4 Ravishankar N 2017-03-02 05:28:12 UTC 
Patches in comment#1 seem to be merged.