[prev in list] [next in list] [prev in thread] [next in thread] 

List:       opensolaris-storage-discuss
Subject:    Re: [storage-discuss] Error talking to target daemon?
From:       Adam Leventhal <ahl () eng ! sun ! com>
Date:       2007-05-08 18:09:39
Message-ID: 20070508180939.GO19256 () eng ! sun ! com
[Download RAW message or body]

Ryan,

Thanks for sending me the core file out of band.

I've filed the following bug:

  6554915 iscsitgtd double frees on target creation errors

The root cause was some knuckleheaded programming:

---8<---

error:
        if (name != NULL)
                free(name);
        if (size != NULL)
                free(size);
        if (alias != NULL)
                free(name);

---8<---

I'm sure someone from the iSCSI team will address this shortly, or I'll
take care of it in a few weeks.

Adam

On Tue, May 08, 2007 at 09:19:47AM -0700, Adam Leventhal wrote:
> Hey Ryan,
> 
> The target daemon may be crashing. Please use coreadm(1M) to enable global
> core dumps (and set the global core pattern). If you can get a core file,
> please send it my way.
> 
> Is there a reason you're not using zfs(1M) to set the shareiscsi property
> on the zvol?
> 
> Adam
> 
> On Tue, May 08, 2007 at 09:56:22AM -0400, Matty wrote:
> > Howdy,
> > 
> > While creating an iSCSI target on system running Nevada build 63, I
> > received the error / warning message "iscsitadm: Unable to contact
> > target daemon":
> > 
> > $ iscsitadm create target -a lucky-tgt0 \
> >                  -b /dev/zvol/dsk/stripedpool/iscsivol000 lucky-tgt0
> > iscsitadm: Unable to contact target daemon
> > 
> > Based on the error message, I thought the create target operation
> > failed. But after reviewing the iscsitadm output, it looks like the
> > target was  created successfully:
> > 
> > $ iscsitadm list target -v
> > Target: lucky-tgt0
> >    iSCSI Name:
> > iqn.1986-03.com.sun:02:1fef830c-841b-6884-8dde-fb2291431880.lucky
> >    Alias: lucky-tgt0
> >    Connections: 0
> >    ACL list:
> >    TPGT list:
> >    LUN information:
> >        LUN: 0
> >            GUID: 0
> >            VID: SUN
> >            PID: SOLARIS
> >            Type: disk
> >            Size: 1.0G
> >            Backing store: /dev/zvol/dsk/stripedpool/iscsivol000
> >            Status: online
> > 
> > Does anyone happen to know what that error means, and what causes it?
> > 
> > Thanks,
> > - Ryan
> > -- 
> > UNIX Administrator
> > http://prefetch.net
> > _______________________________________________
> > storage-discuss mailing list
> > storage-discuss@opensolaris.org
> > http://mail.opensolaris.org/mailman/listinfo/storage-discuss
> 
> -- 
> Adam Leventhal, Solaris Kernel Development       http://blogs.sun.com/ahl
> _______________________________________________
> storage-discuss mailing list
> storage-discuss@opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/storage-discuss

-- 
Adam Leventhal, Solaris Kernel Development       http://blogs.sun.com/ahl
_______________________________________________
storage-discuss mailing list
storage-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/storage-discuss
[prev in list] [next in list] [prev in thread] [next in thread]