Hi Mike,
Thanks for your reply.
It turned out it was something wrong in the IET ietd.conf file. Now
it's working. The following is the working ietd.conf.
Target iqn.2010-01.ca.ualberta.cs.yongjian:lacie.sdb14.3G.0
Lun 0 Path=/dev/sdb14,Type=blockio
Alias DD_test_1
MaxRecvDataSegmentLength 262144
MaxXmitDataSegmentLength 8192
The ietd.conf that was not working was like the following. The
difference is in the 2nd line, marked by [-<The difference>-].
Target iqn.2010-01.ca.ualberta.cs.yongjian:lacie.sdb14.3G.0
Lun 0 Path=/dev/sdb14[-#-],Type=blockio
Alias DD_test_1
MaxRecvDataSegmentLength 262144
MaxXmitDataSegmentLength 8192
The difference is that I tried to comment out everything after /dev/
sdb14. But somehow this confuses IET and/or open-iscsi.
Another not working version is like this:
Target iqn.2010-01.ca.ualberta.cs.yongjian:lacie.sdb14.3G.0
Lun 0 Path=/dev/sdb14,[-Space-]Type=blockio
Alias DD_test_1
MaxRecvDataSegmentLength 262144
MaxXmitDataSegmentLength 8192
The difference between this version and the working one is the space
between the comma and "Type=".
Below is the relevant messages I got from /var/log/messages for IET:
Jan 12 16:51:15 jackz-iSCSI kernel: [ 2991.227443] iscsi_trgt:
Registered io type fileio
Jan 12 16:51:15 jackz-iSCSI kernel: [ 2991.227449] iscsi_trgt:
Registered io type blockio
Jan 12 16:51:15 jackz-iSCSI kernel: [ 2991.227455] iscsi_trgt:
Registered io type nullio
Jan 12 16:51:15 jackz-iSCSI kernel: [ 2991.251724] iscsi_trgt: Target
iqn.2010-01.ca.ualberta.cs.yongjian:lacie.sdb14.3G.0, LUN 0: unknown
param Type=blockio
Jan 12 17:26:02 jackz-iSCSI kernel: [ 5078.173548] iscsi_trgt:
Registered io type fileio
Jan 12 17:26:02 jackz-iSCSI kernel: [ 5078.173555] iscsi_trgt:
Registered io type blockio
Jan 12 17:26:02 jackz-iSCSI kernel: [ 5078.173560] iscsi_trgt:
Registered io type nullio
The following is the
And the following is the relevant messages I got from /var/log/
messages for open-iscsi:
Jan 12 17:11:10 jackz-ubuntu kernel: [ 4211.728589] scsi3 : iSCSI
Initiator over TCP/IP
Jan 12 17:20:41 jackz-ubuntu kernel: [ 4782.525952] scsi4 : iSCSI
Initiator over TCP/IP
Jan 12 17:26:43 jackz-ubuntu kernel: [ 5144.785059] scsi5 : iSCSI
Initiator over TCP/IP
Jan 12 17:27:26 jackz-ubuntu kernel: [ 5188.068083] scsi6 : iSCSI
Initiator over TCP/IP
On Jan 12, 6:35 pm, Mike Christie <micha...@cs.wisc.edu> wrote:
> On 01/12/2010 06:51 PM, Jack Z wrote:
>
>
>
>
>
> > Hi group,
>
> > The iSCSI disk just stops showing up on my computer.
>
> > I'm using open-iscsi again iSCSI Enterprise Target (IET).
>
> > When I do
>
> > $ iscsiadm -m node T<Target> -p<Portal> --login
>
> > everything is fine and the login is always "successful". I also
> > checked the records in IET, which show the login is successful as
> > well.
>
> > However I just can't see the iscsi device any more... It used to be /
> > dev/sdb after the login process. Now there's only /dev/sda, which is
> > the local disk, under /dev which resembles a /dev/sdX style.
>
> > $ fdisk -l
>
> > does not show the iSCSI disk either...
>
> > The OS is Ubuntu 9.04 desktop and open-iscsi version is "2.0-871". The
> > IET version is 0.4.16.
>
> Could you send the ietd.conf and /var/log/messages for the target when
> you start it up and login? And could you send the /var/log/messages for
> the initiator when you login?
--
You received this message because you are subscribed to the Google Groups
"open-iscsi" group.
To post to this group, send email to open-is...@googlegroups.com.
To unsubscribe from this group, send email to
open-iscsi+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/open-iscsi?hl=en.
