On Thu, 2013-01-10 at 00:24 -0600, Mike Christie wrote: > I think some > distros just call iscsi anytime there is a network change like a > interface coming up or a interface getting a address.
Ubuntu (and I'd guess Debian) does this (well, the on ifup part). It also stops open-iscsi on ifdown. I just had to disable that today. Imagine a virtualization host server. You create a new VM on a new VLAN. You add the relevant bridge interface, bring it up, and *bam*, all your existing, running VMs just lost access to their disks. Likewise, you can't upgrade the open-iscsi package while anything is using iSCSI devices, because it will stop and start the service. I solved these problems by using dpkg-divert on the if-up.d and if-down.d scripts to move them to open-iscsi.disabled and a custom policy-rc.d script to disallow open-iscsi stops or restarts if any VMs are running. Also, at least in my case, it's necessary to restart libvirt-bin after restarting open-iscsi. Are many people really using iSCSI via roaming network connectivity? -- Richard
signature.asc
Description: This is a digitally signed message part
