On Mon, May 21, 2012 at 1:26 PM, Vadym Chepkov <[email protected]> wrote: > Hi, > > I am not subscribed to the devel list, so don't think my e-mail will go there.
You know, subscribing only takes a minute, but oh well... > Yes, I have the same pattern in iscsi target and in the store path > > tgtadm --lld iscsi --op show --mode target | grep ^Target > > Target 101: iqn.1999-04.net.videonext:vbuild1 > ... > Target 110: iqn.1999-04.net.videonext:vbuild10 > > > tgtadm --lld iscsi --op show --mode target | grep Backing|grep by-res > Backing store path: /dev/drbd/by-res/vbuild1 > ... > Backing store path: /dev/drbd/by-res/vbuild10 OK, so that seems you only have one LU per target? That's not quite the way it was originally intended, but nonetheless, the RA should of course be able to handle that without breaking. > vbuild[234] have migrated to other node, see what would have happened if I > ran the same command there and had a target called just 'vbuild': > > # tgtadm --lld iscsi --op show --mode target | sed -ne "s/^Target > \([[:digit:]]\+\): iqn.1999-04.net.videonext:vbuild/\1/p" > 1026 > 1032 > 1043 Sure, that's a problem. :) Your patch looks fine to me for STGT; for IET it should be equally trivial but sadly I don't have the capacity to test that at the moment. Anyone able to give IET with an updated agent a spin? Cheers, Florian -- Need help with High Availability? http://www.hastexo.com/now _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
