Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
Hi, I'd like to enable the ko-count option in my drbd.conf on the primary (and secondary). I'd like to test it out and have been unsuccessful at doing so. I've tried to create a logical volume with a drbd device on top of it and when I use dmsetup to: dmsetup suspend <underlying-volume> - nothing happens. It's almost like drbd knows that the volume is suspended and everything is "ok". Even though the write/read calls are blocked on the DRBD primary, nothing is logged, nothing times out. dmsetup rename <underlying volume> - volume renames fine. DRBD doesn't care and continues to function. I think drbd the major/minor numbers, etc. and doesn't care about the name after it's fired up. dmsetup remove -f <underlying volume> - Will not perform this action as DRBD is using it, even with a force. Is there any way I can replicate a secondary going offline in this fashion to test the behaviour? ie. tcp/ip stack is fine, drbd answers the request, sends the write out and the underlying device on the secondary fails to write? I'm stumped. ---- Kris -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.linbit.com/pipermail/drbd-user/attachments/20121030/c5e744fe/attachment.htm>