Å×½ºÆ®¸¦ À§ÇØ »ý¼ºÇÑ Brick À» »èÁ¦ÇÏ°í µ¿ÀÏÇÑ Brick °æ·Î¸¦ ´Ù½Ã »ç¿ëÇÏ°íÀÚ ÇÒ¶§...
# gluster volume create VM_DISK 192.168.200.202:/VM_DISK/HDs 192.168.200.203:/VM_DISK/HDs 192.168.200.204:/VM_DISK/HDs 192.168.200.205:/VM_DISK/HDs
volume create: VM_DISK: failed: /VM_DISK/HDs or a prefix of it is already part of a volume
# setfattr -x trusted.glusterfs.volume-id /VM_DISK/HDs
# setfattr -x trusted.gfid /VM_DISK/HDs
# rm -rf /VM_DISK/HDs/.glusterfs
# gluster volume create VM_DISK 192.168.200.202:/VM_DISK/HDs 192.168.200.203:/VM_DISK/HDs 192.168.200.204:/VM_DISK/HDs 192.168.200.205:/VM_DISK/HDs
volume create: VM_DISK: success: please start the volume to access data
The Solution
For the directory (or any parent directories) that was formerly part of a volume, simply:
setfattr -x trusted.glusterfs.volume-id $brick_path
setfattr -x trusted.gfid $brick_path
rm -rf $brick_path/.glusterfs