gluster
Feature Request - Write unique identifier to each brick to halt if brick is mounted in incorrect location
This is a rookie mistake on my part, however I had bricks mounting in fstab as /dev/sda1, /dev/sdb1, etc vs UUID. After repairing a host issue, it came back online and re-ordered the /dev/sd* drives, causing some bricks to be flipped/mounted to the wrong paths. Much to my surprise, gluster continued to believe those bricks were correct, and began erasing data on those subvolumes. Would be nice if gluster could write some sort of identifier to each brick to halt if that brick process if the ID doesn't match.
Best practice is to use LVM (which has unique name) or FS UUID when mounting. Then, you should create a directory inside the mountpoint, so if the mount operation has failed (or is readonly) GlusterFS would not be able to use the local storage.
You can't trust people to always follow best practices i guess. I think an extra verification as suggested by @edrock200 would be useful.
BTW i found LVM (especially thin provisioned) a horrible monstrosity to work with. Why isn't ZFS recommended yet instead of LVM?
I guess because it's not tested and most probably doesn't have the proper integration (libraries) with ZFS.
I am one of the maintainers of glusterfs, my current employer uses it with zfs. I must say, the experience has been great so far. Marking this for release-12 to see if we get time to get this in.
I am one of the maintainers of glusterfs, my current employer uses it with zfs. I must say, the experience has been great so far. Marking this for release-12 to see if we get time to get this in.
Great! Thank you! Any ETA for v12?