Bug 764917 (GLUSTER-3185)

Summary: object-storage: dht over non-xattr support
Product: [Community] GlusterFS Reporter: Saurabh <saurabh>
Component: object-storageAssignee: Junaid <junaid>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: pre-releaseCC: gluster-bugs, vagarwal
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Saurabh 2011-07-18 02:47:19 UTC 
one more update regarding this bug,


if we take a distribute-replicate volume,
something with this kind of config,

root@Unbuntu:~# /root/glusterfs/inst/sbin/gluster volume info dr1

Volume Name: dr1
Type: Distributed-Replicate
Status: Started
Number of Bricks: 2 x 2 = 4
Transport-type: tcp
Bricks:
Brick1: 10.1.12.25:/mnt/sdb1/d1
Brick2: 10.1.12.25:/mnt/sdb1/r1
Brick3: 10.1.10.154:/mnt/sdb1/d1
Brick4: 10.1.10.154:/mnt/r1
root@Unbuntu:~# 



here brick4 is on a non-xattr supported back-end,

Still data creation happens on all the bricks. 

and if all the bricks except the brick4 are brought down, so GETting data via curl does not happen, as expected  and the bringing them back curl works again to GET data.

But again, should we allow data to get replicated on a brick having no back-end support for xattrs?
Comment 1 Saurabh 2011-07-18 04:47:30 UTC 
Presently if you take a a distribute volume with back end being a mix of having  xattr support and non-xattr support.


the dht allows the all of data to be stored on the brick , the one having the xattr support. 


though no data loss happens, but somewhere if can set some notification of the kind that the other brick is on top of a back-end having  no xattr support, will be better as it may help user replace the brick accordingly.
Comment 2 Anand Avati 2011-10-07 03:35:06 UTC 
CHANGE: http://review.gluster.com/542 (In this case, send setxattr to all the bricks to test user xattr support and return error if setxattr fails on even one of the bricks.) merged in master by Vijay Bellur (vijay)