Description of problem:
=======================
On a distribute-replicate volume set "read-subvolume" volume option to a brick from one of the replicate subvolumes. The same value is applied to rest of the subvolumes also. 

Option: cluster.read-subvolume
Default Value: (null)
Description: inode-read fops happen only on one of the bricks in replicate. Afr will prefer the one specified using this option if it is not stale. Option value must be one of the xlator names of the children. Ex: <volname>-client-0 till <volname>-client-<number-of-bricks - 1>


Expected result:-
=====================
"read-subvolume" volume option should be sub-volume level not for the entire volume 

root@rhs-client11 [Nov-25-2013-10:38:32] >gluster v info vol2
 
Volume Name: vol2
Type: Distributed-Replicate
Volume ID: 459988a6-ae4d-4ac2-ac7d-31282ef446f7
Status: Created
Number of Bricks: 2 x 2 = 4
Transport-type: tcp
Bricks:
Brick1: rhs-client11:/rhs/bricks/vol2-b1
Brick2: rhs-client12:/rhs/bricks/vol2-b1-rep
Brick3: rhs-client11:/rhs/bricks/vol2-b2
Brick4: rhs-client12:/rhs/bricks/vol2-b2-rep
Options Reconfigured:
cluster.read-subvolume: vol2-client-0

Fuse vol file contents:
========================
volume vol2-replicate-0
    type cluster/replicate
    option read-subvolume vol2-client-0
    subvolumes vol2-client-0 vol2-client-1
end-volume

volume vol2-replicate-1
    type cluster/replicate
    option read-subvolume vol2-client-0
    subvolumes vol2-client-2 vol2-client-3
end-volume

Here "vol2-client-0" brick is not applicable for "vol2-replicate-1" subvolume. 

Version-Release number of selected component (if applicable):
==============================================================
glusterfs 3.4.0.43.1u2rhs built on Nov 12 2013 07:38:20