[stgt] Segfault with 2 initiators connecting to 1 target

[FUJITA Tomonori]

On Fri, 14 Sep 2012 05:43:44 +0000
Ty Christensen <tyc at mastermindpro.com> wrote:

> 
> I'm running CentOS 6.3 and the packaged tgtd version 1.0.24 to share out a single target to multiple initiators.  The initiators all use the target as a boot volume, and they're running Windows Embedded with the EWF filter driver filtering out the writes to the volume.  My initiator names are specified by iPXE, and I'm only using the iPXE default so each machine name announces itself uniquely to the target.  I can boot, run, and shutdown a single initiator normally without trouble.
> 
> If I have one initiator booted and start a second, tgtd segfaults when the second node transitions from Windows relying on the iPXE driver to read from the volume to relying on the MS initiator to complete the boot process.  The syslog line states:
> 
> Sep 13 16:33:26 storage kernel: tgtd[1385]: segfault at 1c245a0 ip 0000000001c245a0 sp 00007fffd12b4cb8 error 15

Any other messages?

> I browsed through the commits since version 1.0.24, but I didn't notice anything that indicated a fix for this.  I searched the archives as well, but didn't come up with anyone who seemed to be using multiple initiators pointed to one target.  I looked at the announced IQN on each initiator within Windows, and they are unique.  My questions:
> 
> 1) Multiple initiators pointed to the same target is supported, right?  :^)

It should be.

> 2) Any idea why tgtd segfaulted?
> 3) Is there a chance Windows is lying to me and announcing the same IQN from each initiator since they are running the same image?
> 4) What would you guys need from help to diagnose or troubleshoot this?
> 
> Thanks in advance for your help.  Hopefully I'm not crazy.
--
To unsubscribe from this list: send the line "unsubscribe stgt" in
the body of a message to majordomo at vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html