Hi, I have rbd which contains non-cluster filesystem. If this rbd is mapped+mounted on one host, it should not be mapped+mounted on the other simultaneously. How to protect such rbd from being mapped on the other host? At ceph level the only option is to use "lock add [image-name] [lock-id]" and check for existance of this lock on the other client or is it possible to protect rbd in a way that on other clients "rbd map " command would just fail with something like Permission denied without using arbitrary locks? In other words, can one limit the count of clients that may map certain rbd? Regards, Ugis Racko -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
