Protecting rbd from multiple simultaneous mapping.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



The email thread here : http://www.spinics.net/lists/ceph-devel/msg12226.html discusses a way of preventing multiple simultaneous clients from mapping an rbd via the legacy advisory locking scheme, along with osd blacklisting.

Is it now advisable to use the exclusive lock feature, discussed here : http://lists.ceph.com/pipermail/ceph-users-ceph.com/2015-September/004857.html ?

In other words, does the exclusive lock feature automatically break the lock of any older lock holders and prevent any writes to the rbd from the older holder ?

Another way to frame my question would be : what is the recommended way of preventing multiple simultaneous rbd mappings, based on the state-of-the-art in ceph?

thanks in advance,
- Puneet
_______________________________________________
ceph-users mailing list
ceph-users@xxxxxxxxxxxxxx
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com

[Index of Archives]     [Information on CEPH]     [Linux Filesystem Development]     [Ceph Development]     [Ceph Large]     [Ceph Dev]     [Linux USB Development]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [xfs]


  Powered by Linux