Description of problem: When gluster volume delete is run and removes the volume it leaves behind xattrs that cause a gluster volume create to fail. Version-Release number of selected component (if applicable): glusterfs-server-3.3.0rhs-25.el6rhs.x86_64 How reproducible: Every time. Steps to Reproduce: 1. Run gluster volume delete on a volume 2. Try to create a new volume using the brick from a deleted volume 3. Actual results: ***From the command line*** Create: [root@hp-dl380g7-1 distributed-volume-setup]# gluster volume create distributed-volume hp-dl380g7-1.gsslab.rdu.redhat.com:/brick1 hp-dl380g7-2.gsslab.rdu.redhat.com:/brick1 Creation of volume distributed-volume has been successful. Please start the volume to access data. Delete: [root@hp-dl380g7-1 distributed-volume-setup]# gluster volume delete distributed-volume Deleting volume will erase all information about the volume. Do you want to continue? (y/n) y Deleting volume distributed-volume has been successful And create again: [root@hp-dl380g7-1 distributed-volume-setup]# gluster volume create distributed-volume hp-dl380g7-1.gsslab.rdu.redhat.com:/brick1 hp-dl380g7-2.gsslab.rdu.redhat.com:/brick1 /brick1 or a prefix of it is already part of a volume Expected results: The xattrs are properly cleared so that a volume create can be executed without manually clearing them. Additional info:
*** This bug has been marked as a duplicate of bug 812214 ***