Hello all,

I have been attempting to use the exclusive-lock rbd volume feature to try
to protect against having two QEMUs writing to a volume at the same time.
Specifically if one VM appears to fail due to a net-split, and a second
copy is started somewhere else.

Looking at various mailing list posts and some code patches it looks like
this is not possible currently because if a client doesn't have the lock it
will request it from the lock holder and the lock holder will always give
it up. Therefore the lock will flip back and forth between the clients -
which in the case of a regular filesystem (such as xfs) will lead to
corruption.

Could someone confirm this is the behavior and whether it is possible to
protect the volume in this scenario?
_______________________________________________
ceph-users mailing list
[email protected]
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com

Reply via email to