According to your message you have these bricks:
Bricks:
Brick1: kansas.planet.bn:/gluster_bricks/data/data
Brick2: germany.planet.bn:/gluster_bricks/data/data
Brick3: singapore.planet.bn:/gluster_bricks/data/data
And you tried to reset-brick 'asia.planet.bn:/gluster_bricks/data/data'
which is not in the brick list. The actual name of the device is not important , you just need to mount it on the same location on the same server - otherwise you need the replace-brick operation.
As you haven't mention which brick is broken , I will give you a fictional one.
For example,
the disk/disks at server 'singapore.planet.bn' and mounted at '/gluster_bricks/data/data' has broken.
You replace the disk/disks and mount them at same mount point, so server 'singapore.planet.bn' has a mounted block device at '/gluster_bricks/data/data' and is completely empty.
Then you just run :
gluster volume reset-brick data singapore.planet.bn:/gluster_bricks/data/data start
Which should stop the brick process (if you haven't rebooted the server)
gluster volume reset-brick data singapore.planet.bn:/gluster_bricks/data/data singapore.planet.bn:/gluster_bricks/data/data commit
To restart the processes. You may have to add "force" at the end.
And last ,force a heal:
gluster volume heal data full
Best Regards,
Strahil Nikolov