Bug 856455

Description of problem:
DHT- getfattr ondirectory(from mountpoint) gives error Transport endpoint is not connected, in case of brick down. even though dir is hashed to some other sub-volume which is up
Version-Release number of selected component (if applicable):


How reproducible:
always

Steps to Reproduce:
1. Create a Distributed volume having 3 or more sub-volumes on multiple server and start that volume.

[root@Rhs3 ~]# gluster volume info test
 
Volume Name: test
Type: Distribute
Volume ID: da498fa8-68fc-4de5-a682-07f26eb14c17
Status: Started
Number of Bricks: 3
Transport-type: tcp
Bricks:
Brick1: XX1:/home/test
Brick2: XX2:/home/test
Brick3: XX3:/home/test


2. Fuse Mount the volume from the client-1 using “mount -t glusterfs  server:/<volume> <client-1_mount_point>”

3. From mount point create some dirs and files inside it

4. Find the hash value for dir name and also find its hashed sub volume

[]# getfattr -m . -n trusted.glusterfs.pathinfo /mnt/test
getfattr: Removing leading '/' from absolute path names
# file: /mnt/test
trusted.glusterfs.pathinfo="((<DISTRIBUTE:test-dht> <POSIX(/home/test):Rhs2:/home/test/>) (test-dht-layout (test-client-2 1431655765 2863311529) (test-client-0 2863311530 4294967295) (test-client-1 0 1431655764)))"

hash value for dir 'd10' is 4b423224 
so it should hash to sub-vol 'test-client-1'

5.bring another sub-vol down (hashed sub volume should be up and make cached sub-vol down)


[root@Rhs3 test]# gluster volume status test
Status of volume: test
Gluster process						Port	Online	Pid
------------------------------------------------------------------------------
Brick XX1:/home/test				24009	Y	11463
Brick XX2:/home/test				24009	Y	16287
Brick XX3:/home/test				24009	N	12116
NFS Server on localhost				38467	Y	16293
NFS Server on XXX				38467	Y	16005
NFS Server on xxx				38467	Y	15892

6.from mount point execute getfattr on dir d10
[]# getfattr -m . -n trusted.glusterfs.pathinfo d10
d10: trusted.glusterfs.pathinfo: Transport endpoint is not connected
  
Actual results:
It is only looking at, first cached sub-vol and when it is down, It gives error ' Transport endpoint is not connected'

Expected results:
Directories are created on all sub-vol, so in any case(hashed sub-vol down or cached or any othe sub-vol down), it can get and display xattr value from any other sub-vol

Additional info: