initiator fails to make device entry on fedora core 4

["Randy Pierce" <randy.pierce@xxxxxxxxxxxxxxxxxxxxx>]

Hi All,
I built the linux-iscsi-4.0.2.1 distro on fedora core 4
(2.6.11-1.1369_FC4) and used it to connect to the Intel reference target
(IntelLabs-v20-011504) as a test for upgrading my systems to core 4. I get
a failure of the initiator to establish a device entry in /dev. The
"iscsi-ls -l" command reports a lun and a device ...

*******************************************************************************
SFNet iSCSI Driver Version ...4:0.2.1(15-Mar-2005)
*******************************************************************************
TARGET NAME             : iqn.com.intel.abc123
TARGET ALIAS            : <NULL>
HOST NO                 : 6
TARGET ADDRESS          : 127.0.0.1:3260,1
SESSION STATUS          : CONNECTION ESTABLISHED AT Wed Jun 22 11:17:00
MDT 2005
SESSION ID              : ISID 00023d000001
                          TSIH 1
DEVICE DETAILS:
---------------
LUN NO: 0               : sdb
  Vendor                : Intel
  Model                 : Intel Labs iSCSI
  Rev                   : 0
-------------------------------------------------------------------------------

but there is no /dev/sdb entry!
Here is an excerpt from /var/log/messages...

-------------------------------------------------
Jun 22 11:16:59 demoserver scsi.agent[27394]: Attribute
/sys/devices/platform/host6/target6:0:0/6:0:0:0/type does not exist
Jun 22 11:17:00 demoserver kernel: iscsi-sfnet:host6: Session established
Jun 22 11:17:00 demoserver kernel: sdb: asking for cache data failed
Jun 22 11:17:00 demoserver kernel: sdb: assuming drive cache: write through
Jun 22 11:17:00 demoserver kernel:  sdb: unknown partition table
Jun 22 11:17:00 demoserver kernel: Attached scsi disk sdb at scsi6,
channel 0, id 0, lun 0
Jun 22 11:20:01 demoserver crond(pam_unix)[27500]: session opened for user
root by (uid=0)
Jun 22 11:20:01 demoserver crond(pam_unix)[27501]: session opened for user
root by (uid=0)
Jun 22 11:20:01 demoserver crond(pam_unix)[27501]: session closed for user
root
Jun 22 11:20:02 demoserver crond(pam_unix)[27500]: session closed for user
root
Jun 22 11:25:01 demoserver crond(pam_unix)[27545]: session opened for user
root by (uid=0)
Jun 22 11:25:02 demoserver crond(pam_unix)[27545]: session closed for user
root
Jun 22 11:30:01 demoserver crond(pam_unix)[27590]: session opened for user
root by (uid=0)
Jun 22 11:30:01 demoserver crond(pam_unix)[27591]: session opened for user
root by (uid=0)
Jun 22 11:30:02 demoserver crond(pam_unix)[27591]: session closed for user
root
Jun 22 11:30:02 demoserver crond(pam_unix)[27590]: session closed for user
root
-------------------------------------------

I didn't see anything like this in the archives or bug reports. A google
search didn't produce any hints either. Has anyone else seen this problem?

I did try attaching the same initiator, only built on a core3 system,
running on a core3 system and attaching to the same core4 target and all
was well.

I am trying to figure it out now, but if anyone has a suggestion I would
certainly appreciate it!

-- 
Randy Pierce
Co-Founder / developer
Virtual Storage




-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_idt77&alloc_id492&opÌk
_______________________________________________
linux-iscsi-users mailing list
linux-iscsi-users@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/linux-iscsi-users