Dears, Some days ago, I read about this comands rbd lock add and rbd lock remove , this commands will go maintened in ceph in future versions, or the better form, to use lock in ceph, will go exclusive-lock and this commands will go depreciated ? Thanks a Lot, Marcelo
Em 24/07/2017, Jason Dillaman <jdill...@redhat.com> escreveu:> On Mon, Jul 24, 2017 at 2:15 PM, <li...@marcelofrota.info> wrote: > > 2 questions, > > > > > > > > 1 In the moment i use kernel 4.10, the exclusive-lock not works fine in > > kernel's version less than < 4.12, right ? > > Exclusive lock should work just fine under 4.10 -- but you are trying > to use the new "exclusive" map option that is only available starting > with kernel 4.12. > > > 2 The comand with exclusive > > would this ? > > > > rbd map --exclusive test-xlock3 > > Yes, that should be it. > > > Thanks a Lot, > > > > Marcelo > > > > > > Em 24/07/2017, Jason Dillaman <jdill...@redhat.com> escreveu: > >> You will need to pass the "exclusive" option when running "rbd map" > >> (and be running kernel >= 4.12). > >> > >> On Mon, Jul 24, 2017 at 8:42 AM, <li...@marcelofrota.info> wrote: > >> > I'm testing ceph in my enviroment, but the feature exclusive lock don't > >> > works fine for me or maybe i'm doing something wrong. > >> > > >> > I testing in two machines create one image with exclusive-lock enable, > >> > if I > >> > understood correctly, with this feature, one machine only can mount and > >> > write in image at time. > >> > > >> > But When I'm testing, i saw the lock always is move to machine that try > >> > mount the volume lastly > >> > > >> > Example if i try mount the image in machine1 i see ip the machine1 and i > >> > mount the volume in machine1 : > >> > #rbd lock list test-xlock3 > >> > There is 1 exclusive lock on this image. > >> > Locker ID Address > >> > client.4390 auto XXXXXXXXXXXXXXXX 192.168.0.1:0/2940167630 > >> > > >> > But if now i running rbd map and try mount image in machine2, the lock > >> > is > >> > change to machine2, and i believe this is one error, because if lock > >> > already > >> > in machine one and i write in image, the machine2 don't should can mount > >> > the > >> > same image in the same time. > >> > If i running in machine2 now, i see : > >> > > >> > #rbd lock list test-xlock3 > >> > There is 1 exclusive lock on this image. > >> > Locker ID Address > >> > client.4491 auto XXXXXXXXXXXXXXXXXX 192.168.0.2:0/1260424031 > >> > > >> > > >> > > >> > Exclusive-lock enable in my image : > >> > > >> > rbd info test-xlock3 | grep features > >> > features: exclusive-lock > >> > > >> > > >> > i'm doing some wrong ? Existing some conf, to add in ceph.conf, to fix > >> > this, > >> > if one machine mount the volume, the machine2 don't can in the same > >> > time, i > >> > read about command rbd > >> > lock, but this command seem deprecated. > >> > > >> > > >> > > >> > Thanks, a lot. > >> > Marcelo > >> > > >> > > >> > _______________________________________________ > >> > ceph-users mailing list > >> > ceph-users@lists.ceph.com > >> > http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com > >> > > >> > >> > >> > >> -- > >> Jason > > > > -- > Jason
_______________________________________________ ceph-users mailing list ceph-users@lists.ceph.com http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
