Bug 798198

Description of problem:
Adding a new brick and changing volume to a replicate type with replica 2 to a single brick volume, doesn't cause the new brick to be used. No data gets written to the new brick, already existing files/directories don't get self-healed either by find-stat on the mount-point or by self-heal daemon. The self-heal daemon does heal when "volume heal <vol> full" command is used. But even after that new data isn't written to the new brick.
Only after remounting the volume and restarting the self-heal daemon, the normal operation is restored.

How reproducible:
Always

Steps to Reproduce:
1. create, start and mount a volume with single brick
2. Do some operations on mount point
3. add new brick, #gluster volume add <vol> replica 2 <new-brick>
4. Do more operations on mount point.
  
Actual results:
Older data is not automatically self-healed to the new brick and new data is not replicated to the new brick, until self-heal daemon is restarted and volume is remounted.

Expected results:
Self-heal should happen and new data should be replicated.


Additional info: