clvmd and exclusive locking

[rhurst@xxxxxxxxxxxxxxxxx]

I do not understand how the vgchange/lvchange -aey option gets "enforced" on other nodes that might want to compete for the same clustered VG/lvol resource.  For example, node A exclusively locks and mounts -t ext3 /dev/VGBOOTA/lvol0, but on node B, I can can still lock & mount the same volume -- what gives?  Shouldn't the clvmd disallow such attempts?  Is there a guide that someone can refer me to for such answers?

TIA.

Robert Hurst, Sr. Caché Administrator
Beth Israel Deaconess Medical Center
1135 Tremont Street, REN-7
Boston, Massachusetts   02120-2140
617-754-8754 ∙ Fax: 617-754-8730 ∙ Cell: 401-787-3154
Any technology distinguishable from magic is insufficiently advanced.

Attachment: smime.p7s
Description: S/MIME cryptographic signature

--
Linux-cluster mailing list
Linux-cluster@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/linux-cluster