Starting/stoppin glusterd changes brick pairs
Starting/stoppin glusterd changes brick pairs

the problem was the pair information was not maintained anywhere.
When glusterd re-starts, it reads the brick dir entries and
populates the brick list. adding brick info to volume info file
to fix this issue

Signed-off-by: shishir gowda <shishirng@gluster.com>
Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>

BUG: 1714 ()
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1714

Kaushikbv/Gluster,Kaushikbv/Gluster,Kaushikbv/Gluster