Hi, I'd like to follow up with discussion about concurrent usage iscsiadm tool. It was discussed here about year ago, with suggestion not to use it concurrently [1]. On the other hand, comment [2] says it should be fine. Is the an agreement in open-iscsi community if the concurrent usage of iscsiadm is safe or not? If it's not safe, is there any bug for open-iscsi describing the issue and potential problems if iscsiadm is used concurrently?
The motivation why I'm popping up this again is that in oVirt project [3] we use a lock before calling iscsiadm to make sure it's not run in parallel. This causes us various issues (see e.g. BZ #1787192 [2]) and we'd like to get rid off this lock. I run several thousands tests with our typical usage of iscsiadm [4], running iscsiadm in parallel and haven't spot any issue so far. This suggests removing the lock can be safe, but of course my tests could be just a pure luck. So before removing this lock from our code base, I'd like to know your thoughts about it. Thanks Vojta [1] https://groups.google.com/g/open-iscsi/c/OHOdIm1W274/m/9l5NcPQHBAAJ [2] https://bugzilla.redhat.com/show_bug.cgi?id=1787192#c18 [3] https://www.ovirt.org/ [4] https://github.com/oVirt/vdsm/blob/master/tests/storage/stress/ initiator.py -- You received this message because you are subscribed to the Google Groups "open-iscsi" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/open-iscsi/4882593.9CP3fYhb5E%40localhost.localdomain.
signature.asc
Description: This is a digitally signed message part.
