GlusterFS에서 Volume을 만들었다가 다른 Volume으로 이전 사용했던 Brick을 다시 사용하려고 할 경우,

${brick_path} or a prefix of it is already part of a volume

이와 같은 에러가 뜬다.

해결 방법은,

setfattr -x trusted.glusterfs.volume-id $brick_path
setfattr -x trusted.gfid $brick_path
rm -rf $brick_path/.glusterfs

자세한 내용은 아래 블로그를 참고.

http://joejulian.name/blog/glusterfs-path-or-a-prefix-of-it-is-already-part-of-a-volume/

그 동안 Beta 였던 3.3 버전이 드디어 정식버전으로 릴리즈 되었다.

아래는 3.3 버전에서의 새로워 진 점이다.

Hadoop , Openstack의 Swift와 연동과 replicated+striped 볼륨 타입을 지원하는게 눈에 띈다.


New features

    • Unified File & Object access.
    • Hadoop hooks - HDFS compatibility layer

New Volume Type

    • Repstr - replicated + striped (+ distributed) volumes

Enhancements to Distributed volumes (DHT translator)

    • Rebalance can migrate open files
    • Remove-brick can migrate data to remaining bricks

Enhancements to Replicated volumes (AFR translator)

    • Ability to change replica count on an active volume (possibly including ability to add replication to distribute-only volumes)
    • Granular locking - useful for running VM images needing to be healed. Glusterfs will not have to lock & freeze the whole VM disk image, only the parts that need healing.
    • Proactive self-heal - when a brick comes back online the gluster daemon should begin the self-heal process without waiting for the files to be accessed.
    • Round-trip reduction - should improve performance especially for smaller files.
    • Quorum enforcement - should help resolve or avoid split brain scenarios



+ Recent posts