Re: iscsi connection error

2009-06-15 Thread sundar mahadevan

Hi Mike,
First my apologies for a late reply. I have resolved this issue. I
changed the install locations and it worked. Earlier i tried shared
home install. Basically, i had a shared oracle home and tried to
install the oracle software (binaries) to be shared by both nodes. But
later i installed the oracle softwares separate on both the nodes and
they worked fine. Appreciate your sincere efforts to help noobs like
me.

On Thu, Jun 11, 2009 at 1:02 PM, Mike Christiemicha...@cs.wisc.edu wrote:

 On 06/10/2009 10:49 AM, sundar mahadevan wrote:
 Hi Members,
 First of all, I'm not too sure if this question is supposed to raise
 here. Sorry if this is not the right place. Appreciate if you could
 direct me to the right place. Thanks.

 OS: Oracle enterprise linux
 rpm -qa | grep -i scsi

 scsi-target-utils-0.0-5.20080917snap.el5
 iscsi-initiator-utils-6.2.0.868-0.18.el5


 what kernel are you using (do uname -a)?

 I'm trying to install oracle 9i rac. During instllation half way
 through, i receive the following error messages. I encountered this
 problem twice. In fact on the second attempt, the connection got
 dropped at 10:54 and then somehow reconnected itself in a few seconds.
 But later the connection dropped and did not comeback again. Please
 help. Noob. Thanks in advance.

 Jun 10 10:54:37 sunny1pub kernel:  connection1:0: iscsi: detected conn
 error (1011)
 .
 .
 .
 Jun 10 10:54:40 sunny1pub iscsid: connection1:0 is operational after
 recovery (1 attempts)


 Jun 10 10:27:14 sunny1pub kernel: o2net: accepted connection from node
 sunny2pub.ezhome.com (num 1) at 10.1.1.2:
 Jun 10 10:27:18 sunny1pub kernel: ocfs2_dlm: Node 1 joins domain
 1B9768E4C4FC4165A22E5E95E6A93F80
 Jun 10 10:27:18 sunny1pub kernel: ocfs2_dlm: Nodes in domain
 (1B9768E4C4FC4165A22E5E95E6A93F80): 0 1
 Jun 10 10:54:37 sunny1pub kernel:  connection1:0: iscsi: detected conn
 error (1011)
 Jun 10 10:54:37 sunny1pub iscsid: Kernel reported iSCSI connection 1:0
 error (1011) state (3)
 Jun 10 10:54:37 sunny1pub tgtd: abort_task_set(979) found a01 0
 Jun 10 10:54:37 sunny1pub tgtd: conn_close(88) connection closed 0x9e370c4 2
 Jun 10 10:54:39 sunny1pub kernel: iscsi: host reset succeeded


 Is the initiator connected to the target running on the same box?


 It looks like a command took too long. If a command takes longer than
 the scsi command timeout (/sys/block/sdX/device/timeout) then the scsi
 layer will try to abort it (if that fails reset the lun and if that
 fails reset the host).


 Jun 10 10:54:40 sunny1pub iscsid: received iferror -38
 Jun 10 10:54:40 sunny1pub last message repeated 2 times
 Jun 10 10:54:40 sunny1pub iscsid: connection1:0 is operational after
 recovery (1 attempts)
 Jun 10 10:57:57 sunny1pub kernel: ping timeout of 5 secs expired, last
 rx 1740985, last ping 1745985, now 1750985

 The initiator sends a iscsi nop as a ping every x seconds. If we do not
 get a response we drop the sesison, try to relogin and retry the IO.

 Jun 10 10:57:57 sunny1pub kernel:  connection1:0: iscsi: detected conn
 error (1011)
 Jun 10 10:57:59 sunny1pub iscsid: Kernel reported iSCSI connection 1:0
 error (1011) state (3)
 Jun 10 10:59:58 sunny1pub kernel:  session1: iscsi: session recovery
 timed out after 120 secs

 it looks like something happened to the target or connection. We were
 not able to log back in after trying for 2 minutes
 (node.session.replacement_timeout).

 Jun 10 10:59:58 sunny1pub kernel: iscsi: cmd 0x2a is not queued (8)
 Jun 10 11:06:10 sunny1pub syslogd 1.4.1: restart.

 


 


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
open-iscsi group.
To post to this group, send email to open-iscsi@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
-~--~~~~--~~--~--~---



Re: open-iscsi initiator machine hangs when iscsitarget is rebooted

2009-05-14 Thread sundar mahadevan

@Ulrich,
Were you exporting something on ocfs using the iscsi-target?
If you had meant any data transfer between the boxes using
iscsi-target,  there were no data transfers between them.

I tried the suggestion you gave me. It works perfect. Once i stopped
the service, it says connect failed(111) and keeps trying and once the
service is up, the error goes off and it says connection 1 is
operational after 10 attempts.
The same case with the iscsitarget/initiator box reboot as well.

On Thu, May 14, 2009 at 1:14 PM, Mike Christie micha...@cs.wisc.edu wrote:

 sundar mahadevan wrote:
 Hi members,
 I tried to do the following to find out the error messages:

 Both systems with iscsitarget/open-iscsi initiator and open-iscsi
 initiator were up.
 On the open-iscsi initiator i had opened a terminal with command tail
 -f /var/log/messages and left it running
 And then i rebooted the server with iscsitarget/open-iscsi initiator

 And all i could see were

 ocfs2_dlm node 0 leaves domain
 nodes in domain : 1
 and then it hangs again
 so i had to manually hard reset the server

 I tried to boot with runlevel 2 but there were not much of a use
 because there were no specific error messages to this scenario, i
 Checked /var/log/messages and /var/log/boot.omsg

 But i'm still able to ping the open-iscsi initiator system on its
 hang. But when i try to rsh or ssh to the system, nothing happens.

 I haven't setup multipath yet.

 @mike
 I have setup ocfs2 file system on a partition(on  secondary hard drive
 on iscsitarget/open-iscsi initiator box) which is being mounted as
 /u01/orcl on both boxes.
 So i think i have nbd(not sure if my setup is supposed to be called as nbd).


 nbd is a special network block device driver. Do not worry about it. It
 does not look like you have it.

 When i tried rciscsitarget stop on  iscsitarget/open-iscsi initiator
 box, both the  iscsitarget/open-iscsi initiator box and  open-iscsi
 initiator box hanged. Again a hard reset.


 Were you exporting something on ocfs using the iscsi-target?

 Could you simplify this and take ocfs out for a minute. Just add some
 file or real disk or a virtual disk to the ietd.conf file for the lun.

 For example just stick:
 Lun 0 Type=nullio,Sectors=2097152
 in the ietd.conf which will create a dummy lun.

 Then restart the target and log in from the other box and retry your
 reboot test with that (no ocfcs2 at all).

 Does that hang?

 


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
open-iscsi group.
To post to this group, send email to open-iscsi@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
-~--~~~~--~~--~--~---



open-iscsi initiator machine hangs when iscsitarget is rebooted

2009-05-11 Thread sundar mahadevan

Hi member,
I run a test environment with 2 servers running opensuse 11.1(one has
iscsitarget/open-iscsi initiator and other has open-iscsi initiator).
Usually, I shutdown the open-iscsi initiator server first and then the
other server with iscsitarget/open-iscsi initiator. But whenever i
reboot the server with iscsitarget/open-iscsi initiator, the other
server with open-iscsi initiator hangs completely even after the
server with iscsitarget/open-iscsi initiator comes back after a
reboot. Is this a normal behaviour? Because of the server hang, i'm
unable to check the logs and always have to go for a hard
reset/shutdown. noob. help pls.

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
open-iscsi group.
To post to this group, send email to open-iscsi@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
-~--~~~~--~~--~--~---



Re: open-iscsi does not detect logical volume

2009-05-01 Thread sundar mahadevan

@mike:
When you run service iscsi-target start to start IET, do you see any
errors in /var/log/messages?
Yes.
May  1 09:57:55 sunny2 kernel: iSCSI Enterprise Target Software - version 0.4.16
May  1 09:57:55 sunny2 kernel: iscsi_trgt: Registered io type fileio
May  1 09:57:55 sunny2 kernel: iscsi_trgt: Registered io type blockio
May  1 09:57:55 sunny2 kernel: iscsi_trgt: Registered io type nullio
May  1 09:57:55 sunny2 kernel: iscsi_trgt: open_path(119) Can't open
/dev/vg/ocfs -2
May  1 09:57:55 sunny2 kernel: iscsi_trgt: fileio_attach(283) -2
May  1 09:57:55 sunny2 ietd: Can't create a logical unit 2 1 0
Path=/dev/vg/ocfs,Type=fileio

cd /home/sunny/Desktop
dd if=/dev/zero of=test bs=1G count=1

opened ietd.conf and did

Target iqn.2009-09.com.ezhome:ocfs
   Lun 0 Path=/home/sunny/Desktop/test,Type=fileio


service iscsi-target stop
service iscsi-target start

May  1 10:15:37 sunny2 kernel: iSCSI Enterprise Target Software - version 0.4.16
May  1 10:15:37 sunny2 kernel: iscsi_trgt: Registered io type fileio
May  1 10:15:37 sunny2 kernel: iscsi_trgt: Registered io type blockio
May  1 10:15:37 sunny2 kernel: iscsi_trgt: Registered io type nullio

iscsiadm -m session -P 3

iSCSI Transport Class version 2.0-870
iscsiadm version 2.0-870
Target: iqn.2009-09.com.ezhome:ocfs
Current Portal: 10.1.1.1:3260,1
Persistent Portal: 10.1.1.1:3260,1
**
Interface:
**
Iface Name: default
Iface Transport: tcp
Iface Initiatorname: iqn.1996-04.de.suse:01:79a5ecb15528
Iface IPaddress: 10.1.1.2
Iface HWaddress: default
Iface Netdev: default
SID: 1
iSCSI Connection State: LOGGED IN
iSCSI Session State: LOGGED_IN
Internal iscsid Session State: NO CHANGE

Negotiated iSCSI params:

HeaderDigest: None
DataDigest: None
MaxRecvDataSegmentLength: 131072
MaxXmitDataSegmentLength: 8192
FirstBurstLength: 65536
MaxBurstLength: 262144
ImmediateData: Yes
InitialR2T: Yes
MaxOutstandingR2T: 1

Attached SCSI devices:

Host Number: 2  State: running

But there are no messages in /var/log/messages about new disk getting added.

I even tried

sunny1:~ # iscsiadm -m node -T iqn.2009-09.com.ezhome:ocfs -p 10.1.1.1 -l
Logging in to [iface: default, target: iqn.2009-09.com.ezhome:ocfs,
portal: 10.1.1.1,3260]
iscsiadm: Could not login to [iface: default, target:
iqn.2009-09.com.ezhome:ocfs, portal: 10.1.1.1,3260]:
iscsiadm: initiator reported error (15 - already exists)
sunny1:~ #

/var/log/messages - May  1 10:21:11 sunny1 iscsid: session
[iqn.2009-09.com.ezhome:ocfs,10.1.1.1,3260] already running.

Help pls!

On Thu, Apr 30, 2009 at 3:38 PM, Mike Christie micha...@cs.wisc.edu wrote:

 Mike Christie wrote:
 sundar mahadevan wrote:
 As i said before, there is no real file for /dev/vg/ocfs
 but
 lvdisplay shows /dev/vg/ocfs as my logical volume
 and
 ls -ail /dev/vg/ocfs
 35413 lrwxrwxrwx 1 root root 19 Apr 30 14:33 /dev/vg/ocfs - 
 /dev/mapper/vg-ocfs

 Now i'm really confused.
 Mike: As i said before there are only 2 uncommented lines in /etc/ietd.conf

 Target iqn.2009-09.com.ezhome:ocfs
         Lun 0 Path=/dev/vg/ocfs,Type=fileio

 When you run service iscsi-target start to start IET, do you see any
 errors in /var/log/messages?


 You might just want to try something simple first.

 - dd if=/dev/zero of=file bs=1G count=1
 - open ietd.conf and do

 Target iqn.2009-09.com.ezhome:ocfs
        Lun 0 Path=/where_you_put_file/file,Type=fileio


 service iscsi-target stop
 service iscsi-target start

 then on the initiator try to login. Do you see a disk getting added in
 /var/log/messages. if you do iscsiadm -m session -P 3 do you see your disk?

 


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
open-iscsi group.
To post to this group, send email to open-iscsi@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
-~--~~~~--~~--~--~---



Re: open-iscsi does not detect logical volume

2009-05-01 Thread sundar mahadevan

Hi All,
I have figured out what the problem is:
On reboot i found out that the volume group becomes inactive. So i did
a vgchange -a y and it becomes active and restart both iscsitarget and
open-iscsi services and you are good to go. Many Thanks to mike and
Konrad for helping me out. I haven't yet figured out as to why the
volume group goes inactive on reboot and how to automate this process
of activating it on reboot. Thanks to one and all who helped me
resolve this issue. I believe this is an issue with opensuse.

On Fri, May 1, 2009 at 10:44 AM, sundar mahadevan
sundarmahadeva...@gmail.com wrote:
 @mike:
 it works fine now. i restarted the service in the initiator and there
 is a new device detected in /var/log/messages as well as in fdisk -l
 What do i do now for this to work with logical volume. any help is
 greatly appreciated. many thanks for your help, mike.

 On Fri, May 1, 2009 at 10:36 AM, sundar mahadevan
 sundarmahadeva...@gmail.com wrote:
 @mike:
 When you run service iscsi-target start to start IET, do you see any
 errors in /var/log/messages?
 Yes.
 May  1 09:57:55 sunny2 kernel: iSCSI Enterprise Target Software - version 
 0.4.16
 May  1 09:57:55 sunny2 kernel: iscsi_trgt: Registered io type fileio
 May  1 09:57:55 sunny2 kernel: iscsi_trgt: Registered io type blockio
 May  1 09:57:55 sunny2 kernel: iscsi_trgt: Registered io type nullio
 May  1 09:57:55 sunny2 kernel: iscsi_trgt: open_path(119) Can't open
 /dev/vg/ocfs -2
 May  1 09:57:55 sunny2 kernel: iscsi_trgt: fileio_attach(283) -2
 May  1 09:57:55 sunny2 ietd: Can't create a logical unit 2 1 0
 Path=/dev/vg/ocfs,Type=fileio

 cd /home/sunny/Desktop
 dd if=/dev/zero of=test bs=1G count=1

 opened ietd.conf and did

 Target iqn.2009-09.com.ezhome:ocfs
       Lun 0 Path=/home/sunny/Desktop/test,Type=fileio


 service iscsi-target stop
 service iscsi-target start

 May  1 10:15:37 sunny2 kernel: iSCSI Enterprise Target Software - version 
 0.4.16
 May  1 10:15:37 sunny2 kernel: iscsi_trgt: Registered io type fileio
 May  1 10:15:37 sunny2 kernel: iscsi_trgt: Registered io type blockio
 May  1 10:15:37 sunny2 kernel: iscsi_trgt: Registered io type nullio

 iscsiadm -m session -P 3

 iSCSI Transport Class version 2.0-870
 iscsiadm version 2.0-870
 Target: iqn.2009-09.com.ezhome:ocfs
        Current Portal: 10.1.1.1:3260,1
        Persistent Portal: 10.1.1.1:3260,1
                **
                Interface:
                **
                Iface Name: default
                Iface Transport: tcp
                Iface Initiatorname: iqn.1996-04.de.suse:01:79a5ecb15528
                Iface IPaddress: 10.1.1.2
                Iface HWaddress: default
                Iface Netdev: default
                SID: 1
                iSCSI Connection State: LOGGED IN
                iSCSI Session State: LOGGED_IN
                Internal iscsid Session State: NO CHANGE
                
                Negotiated iSCSI params:
                
                HeaderDigest: None
                DataDigest: None
                MaxRecvDataSegmentLength: 131072
                MaxXmitDataSegmentLength: 8192
                FirstBurstLength: 65536
                MaxBurstLength: 262144
                ImmediateData: Yes
                InitialR2T: Yes
                MaxOutstandingR2T: 1
                
                Attached SCSI devices:
                
                Host Number: 2  State: running

 But there are no messages in /var/log/messages about new disk getting added.

 I even tried

 sunny1:~ # iscsiadm -m node -T iqn.2009-09.com.ezhome:ocfs -p 10.1.1.1 -l
 Logging in to [iface: default, target: iqn.2009-09.com.ezhome:ocfs,
 portal: 10.1.1.1,3260]
 iscsiadm: Could not login to [iface: default, target:
 iqn.2009-09.com.ezhome:ocfs, portal: 10.1.1.1,3260]:
 iscsiadm: initiator reported error (15 - already exists)
 sunny1:~ #

 /var/log/messages - May  1 10:21:11 sunny1 iscsid: session
 [iqn.2009-09.com.ezhome:ocfs,10.1.1.1,3260] already running.

 Help pls!

 On Thu, Apr 30, 2009 at 3:38 PM, Mike Christie micha...@cs.wisc.edu wrote:

 Mike Christie wrote:
 sundar mahadevan wrote:
 As i said before, there is no real file for /dev/vg/ocfs
 but
 lvdisplay shows /dev/vg/ocfs as my logical volume
 and
 ls -ail /dev/vg/ocfs
 35413 lrwxrwxrwx 1 root root 19 Apr 30 14:33 /dev/vg/ocfs - 
 /dev/mapper/vg-ocfs

 Now i'm really confused.
 Mike: As i said before there are only 2 uncommented lines in 
 /etc/ietd.conf

 Target iqn.2009-09.com.ezhome:ocfs
         Lun 0 Path=/dev/vg/ocfs,Type=fileio

 When you run service iscsi-target start to start IET, do you see any
 errors in /var/log/messages?


 You might just want to try something simple first.

 - dd if=/dev/zero of=file bs=1G count=1
 - open ietd.conf and do

 Target iqn.2009-09.com.ezhome:ocfs
        Lun 0 Path=/where_you_put_file/file,Type=fileio


 service iscsi-target stop

open-iscsi does not detect logical volume

2009-04-30 Thread sundar mahadevan

Hi,
I have iscsitarget(0.4.15-89.10) installed on system 1(opensuse 11.1)
with firewall allowing port 3260 and open-iscsi(2.0.870-21.1)
installed on system 2(opensuse 11.1).

Here is my command from client:
sunny1:/etc/iscsi/ifaces # iscsiadm -m node -T
iqn.2009-09.com.ezhome:ocfs -p 10.1.1.1 -l
Logging in to [iface: default, target: iqn.2009-09.com.ezhome:ocfs,
portal: 10.1.1.1,3260]
Login to [iface: default, target: iqn.2009-09.com.ezhome:ocfs, portal:
10.1.1.1,3260]: successful

But i don't see the logical volume detected when i issue fdisk -l
Also there are no error messages in /var/log/messages
cat /var/log/messages | tail -n 20
...
...
Apr 30 12:13:23 sunny1 kernel: scsi4 : iSCSI Initiator over TCP/IP
Apr 30 12:13:24 sunny1 iscsid: connection3:0 is operational now

Newbie. Please help. Thanks in advance.

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
open-iscsi group.
To post to this group, send email to open-iscsi@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
-~--~~~~--~~--~--~---



Re: open-iscsi does not detect logical volume

2009-04-30 Thread sundar mahadevan

As i said before, there is no real file for /dev/vg/ocfs
but
lvdisplay shows /dev/vg/ocfs as my logical volume
and
ls -ail /dev/vg/ocfs
35413 lrwxrwxrwx 1 root root 19 Apr 30 14:33 /dev/vg/ocfs - /dev/mapper/vg-ocfs

Now i'm really confused.
Mike: As i said before there are only 2 uncommented lines in /etc/ietd.conf

Target iqn.2009-09.com.ezhome:ocfs
Lun 0 Path=/dev/vg/ocfs,Type=fileio

Please help

On Thu, Apr 30, 2009 at 1:53 PM, sundar mahadevan
sundarmahadeva...@gmail.com wrote:
 I realise what my problem is. Earlier i used ubuntu and In ubuntu when
 a new logical volume is created, it is listed under /dev/vg/ocfs where
 vg is the volume group and ocfs is the logical volume. In opensuse, I
 'm unable to find out what/where my logical volume is:

 I had mentioned Path=/dev/vg/ocfs in /etc/ietd.conf which does not exist.

 Target iqn.2009-09.com.ezhome:ocfs
        Lun 0 Path=/dev/vg/ocfs,Type=fileio

 Thanks to Mike for guiding me in the right direction. I belive this is
 the problem. Experts, your inputs on how the logical volumes are
 mapped in opensuse please...

 On Thu, Apr 30, 2009 at 1:23 PM, Konrad Rzeszutek
 kon...@virtualiron.com wrote:

 On Thu, Apr 30, 2009 at 12:16:16PM -0400, sundar mahadevan wrote:

 Hi,
 I have iscsitarget(0.4.15-89.10) installed on system 1(opensuse 11.1)
 with firewall allowing port 3260 and open-iscsi(2.0.870-21.1)
 installed on system 2(opensuse 11.1).

 Here is my command from client:
 sunny1:/etc/iscsi/ifaces # iscsiadm -m node -T
 iqn.2009-09.com.ezhome:ocfs -p 10.1.1.1 -l
 Logging in to [iface: default, target: iqn.2009-09.com.ezhome:ocfs,
 portal: 10.1.1.1,3260]
 Login to [iface: default, target: iqn.2009-09.com.ezhome:ocfs, portal:
 10.1.1.1,3260]: successful

 But i don't see the logical volume detected when i issue fdisk -l

 You won't see it that way. The LVM metadata is not in the MBR, but
 in the first 384 sectors, in its own format. You need to do 'pvscan' to see 
 your logical
 volumes. And after as well do 'vgchange -a ly' after the scan.

 Also there are no error messages in /var/log/messages
 cat /var/log/messages | tail -n 20
 ...
 ...
 Apr 30 12:13:23 sunny1 kernel: scsi4 : iSCSI Initiator over TCP/IP
 Apr 30 12:13:24 sunny1 iscsid: connection3:0 is operational now

 Newbie. Please help. Thanks in advance.



 



--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
open-iscsi group.
To post to this group, send email to open-iscsi@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
-~--~~~~--~~--~--~---



Re: open-iscsi created only one disk but missing 2 more

2009-04-17 Thread sundar mahadevan

Hi All,
I tried different things to go past the errors. Now I received a
different error.

I changed my setup. Earlier i had a cross over cable with static ip
connection between the 2 systems but now i have connected the systems
to a router with dhcp. And the error is as follows: Please help.

As usual i receive this error with the following command:
iscsiadm -m session

Apr 17 11:40:42 sunny1 iscsid: Could not get host for sid 1.
Apr 17 11:40:42 sunny1 iscsid: could not get host_no for session 6.
Apr 17 11:40:42 sunny1 iscsid: could not find session info for session1

And here is the major error: now there are no devices detected. I
tried switching another hard disk too (thinking that it might be a
problem with the hard disk) but the same error again.

Apr 17 11:40:42 sunny1 iscsid: session
[iqn.2009-09.com.ubuntu:asm,192.168.2.3,3260] already running.
Apr 17 11:40:44 sunny1 kernel: [ 5661.360412] sd 2:0:0:0: [sdb]
Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK,SUGGEST_OK
Apr 17 11:40:44 sunny1 kernel: [ 5661.360436] end_request: I/O error,
dev sdb, sector 0
Apr 17 11:40:44 sunny1 kernel: [ 5661.360449] __ratelimit: 2 callbacks
suppressed
Apr 17 11:40:44 sunny1 kernel: [ 5661.360457] Buffer I/O error on
device sdb, logical block 0
Apr 17 11:40:44 sunny1 kernel: [ 5661.360471] Buffer I/O error on
device sdb, logical block 1
Apr 17 11:40:44 sunny1 kernel: [ 5661.360478] Buffer I/O error on
device sdb, logical block 2
Apr 17 11:40:44 sunny1 kernel: [ 5661.360486] Buffer I/O error on
device sdb, logical block 3
Apr 17 11:40:44 sunny1 kernel: [ 5661.370342] sd 2:0:0:0: [sdb]
Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK,SUGGEST_OK
Apr 17 11:40:44 sunny1 kernel: [ 5661.370359] end_request: I/O error,
dev sdb, sector 0
Apr 17 11:40:44 sunny1 kernel: [ 5661.370369] Buffer I/O error on
device sdb, logical block 0
Apr 17 11:40:44 sunny1 kernel: [ 5661.375106] sd 2:0:0:0: [sdb]
Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK,SUGGEST_OK
Apr 17 11:40:44 sunny1 kernel: [ 5661.375125] end_request: I/O error,
dev sdb, sector 33554424
Apr 17 11:40:44 sunny1 kernel: [ 5661.375135] Buffer I/O error on
device sdb, logical block 4194303
Apr 17 11:40:44 sunny1 kernel: [ 5661.379983] sd 2:0:0:0: [sdb]
Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK,SUGGEST_OK
Apr 17 11:40:44 sunny1 kernel: [ 5661.380022] end_request: I/O error,
dev sdb, sector 33554424
Apr 17 11:40:44 sunny1 kernel: [ 5661.380032] Buffer I/O error on
device sdb, logical block 4194303
Apr 17 11:40:44 sunny1 kernel: [ 5661.385049] sd 2:0:0:0: [sdb]
Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK,SUGGEST_OK
Apr 17 11:40:44 sunny1 kernel: [ 5661.385069] end_request: I/O error,
dev sdb, sector 0
Apr 17 11:40:44 sunny1 kernel: [ 5661.385079] Buffer I/O error on
device sdb, logical block 0
Apr 17 11:40:44 sunny1 kernel: [ 5661.389754] sd 2:0:0:0: [sdb]
Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK,SUGGEST_OK
Apr 17 11:40:44 sunny1 kernel: [ 5661.389773] end_request: I/O error,
dev sdb, sector 8
Apr 17 11:40:44 sunny1 kernel: [ 5661.389782] Buffer I/O error on
device sdb, logical block 1
Apr 17 11:40:44 sunny1 kernel: [ 5661.394365] sd 2:0:0:0: [sdb]
Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK,SUGGEST_OK
Apr 17 11:40:44 sunny1 kernel: [ 5661.394383] end_request: I/O error,
dev sdb, sector 16
Apr 17 11:40:44 sunny1 kernel: [ 5661.394392] Buffer I/O error on
device sdb, logical block 2
Apr 17 11:40:44 sunny1 kernel: [ 5661.397706] sd 2:0:0:0: [sdb]
Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK,SUGGEST_OK
Apr 17 11:40:44 sunny1 kernel: [ 5661.397722] end_request: I/O error,
dev sdb, sector 24
Apr 17 11:40:44 sunny1 kernel: [ 5661.397743] sd 2:0:0:0: [sdb]
Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK,SUGGEST_OK
Apr 17 11:40:44 sunny1 kernel: [ 5661.397753] end_request: I/O error,
dev sdb, sector 0
r...@sunny1:/home/sunny#

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
open-iscsi group.
To post to this group, send email to open-iscsi@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
-~--~~~~--~~--~--~---



Re: open-iscsi created only one disk but missing 2 more

2009-04-16 Thread sundar mahadevan

Hi,
Please find my answers below: Appreciate you help.

 What Target are you using?

both the systems are ubuntu 8.10

I beat my head on a issue when I first
 setup regarding access permissions. If you don't have the permissions
 right on the array, open-iscsi will let you see it but not log in.

I 'm logged in as root and have executed all the commands. When you
say array, fyi it is just a secondary hard drive conencted to the
system.

 Another thing you may want to check, if you are sharing luns between
 systems, some arrays require you to explicitly allow that behavior.

Is there a command for that? how do i check if i need to explicitly
allow sharing?

 And last but not least, if you have a backend and a front end
 connection make sure you are connecting to the array with the right
 interface. Make sure one connection does not have a matching MTU
 *jumbo frames with the array it can cause strange behavior.

I'm sorry i 'm unable to understand this(if you could elaborate on
this pls: newbie). But to make things simple, my scenario is as
follows: Home pcs(900Mhz/512MB RAM/P3): 2 systems with ubuntu 8.10
with both open-iscsi installed.

On System 1 : i attached a second hard drive of size 20G. I installed
lvm2 and I created 1 physical volume of size 20G, 1 volume group vg1
and then created 3 logical volumes /dev/vg1/asm 17G, /dev/vg1/ocr 960M
and /dev/vg1/vote 750M.

On System 2: executed commands:

iscsiadm -m discovery -t st -p 192.168.20.22
The output was:
192.168.20.22:3260,1 iqn.2001-04.com.ubuntu:scsi.disk.vg.asm
192.168.20.22:3260,1 iqn.2001-04.com.ubuntu:scsi.disk.vg.ocr
192.168.20.22:3260,1 iqn.2001-04.com.ubuntu:scsi.disk.vg.vote

iscsiadm -m node -T iqn.2001-04.com.ubuntu:scsi.disk.vg.asm -p 192.168.20.22 -l
Output: Login session [iface: default, target:
iqn.2001-04.com.ubuntu:scsi.disk.vg.asm, portal: 192.168.20.22,3260]

iscsiadm -m node -T iqn.2001-04.com.ubuntu:scsi.disk.vg.vote -p 192.168.20.22 -l
Output: Login session [iface: default, target:
iqn.2001-04.com.ubuntu:scsi.disk.vg.vote, portal: 192.168.20.22,3260]

iscsiadm -m node -T iqn.2001-04.com.ubuntu:scsi.disk.vg.ocr -p 192.168.20.22 -l
Output: Login session [iface: default, target:
iqn.2001-04.com.ubuntu:scsi.disk.vg.ocr, portal: 192.168.20.22,3260]

I must really thank you for having replied me. I was just feeling bad
that no one replied me on this issue. Thank you so much.

 On Apr 15, 10:27 pm, sundar mahadevan sundarmahadeva...@gmail.com
 wrote:
 I tried the same connecting another hard drive of 20 G with 3 logical
 volumes namely: asm 17G , ocr 924M and vote 760M.

 iscsiadm -m node -T iqn.2001-04.com.ubuntu:scsi.disk.vg1.ocr -p 
 192.168.20.22 -l
 iscsiadm -m node -T iqn.2001-04.com.ubuntu:scsi.disk.vg1.vote -p
 192.168.20.22 -l
 iscsiadm -m node -T iqn.2001-04.com.ubuntu:scsi.disk.vg1.asm -p 
 192.168.20.22 -l

 Looks like it only created the first one: ocr

 Here is the log from /var/log/syslog
 Apr 15 21:10:17 sunny2 kernel: [ 1603.409561] Loading iSCSI transport
 class v2.0-870.
 Apr 15 21:10:17 sunny2 kernel: [ 1603.486634] iscsi: registered transport 
 (tcp)
 Apr 15 21:10:18 sunny2 kernel: [ 1603.848719] iscsi: registered transport 
 (iser)
 Apr 15 21:10:18 sunny2 iscsid: iSCSI logger with pid=5912 started!
 Apr 15 21:10:18 sunny2 kernel: [ 1604.408284] scsi2 : iSCSI Initiator
 over TCP/IP
 Apr 15 21:10:19 sunny2 iscsid: transport class version 2.0-870. iscsid
 version 2.0-865
 Apr 15 21:10:19 sunny2 iscsid: iSCSI daemon with pid=5914 started!
 Apr 15 21:10:19 sunny2 iscsid: Could not verify connection 1:2. Dropping 
 event.
 Apr 15 21:10:19 sunny2 iscsid: Could not verify connection 1:2. Dropping 
 event.
 Apr 15 21:10:20 sunny2 kernel: [ 1606.064265] scsi3 : iSCSI Initiator
 over TCP/IP
 Apr 15 21:10:21 sunny2 iscsid: Could not verify connection 2:3. Dropping 
 event.
 Apr 15 21:10:21 sunny2 iscsid: Could not verify connection 2:3. Dropping 
 event.
 Apr 15 21:10:21 sunny2 kernel: [ 1607.592257] scsi4 : iSCSI Initiator
 over TCP/IP
 Apr 15 21:10:22 sunny2 iscsid: Could not verify connection 3:4. Dropping 
 event.
 Apr 15 21:10:22 sunny2 iscsid: Could not verify connection 3:4. Dropping 
 event.
 Apr 15 21:10:23 sunny2 kernel: [ 1609.120249] scsi5 : iSCSI Initiator
 over TCP/IP
 Apr 15 21:10:24 sunny2 iscsid: Could not verify connection 4:5. Dropping 
 event.
 Apr 15 21:10:24 sunny2 iscsid: Could not verify connection 4:5. Dropping 
 event.
 Apr 15 21:15:00 sunny2 kernel: [ 1886.664257] scsi6 : iSCSI Initiator
 over TCP/IP
 Apr 15 21:15:01 sunny2 iscsid: Could not verify connection 5:6. Dropping 
 event.
 Apr 15 21:15:01 sunny2 kernel: [ 1886.946886] scsi 6:0:0:0:
 Direct-Access     IET      VIRTUAL-DISK     0    PQ: 0 ANSI: 4
 Apr 15 21:15:01 sunny2 kernel: [ 1886.952267] sd 6:0:0:0: [sdb]
 1892352 512-byte hardware sectors (969 MB)
 Apr 15 21:15:01 sunny2 kernel: [ 1886.956338] sd 6:0:0:0: [sdb] Write
 Protect is off
 Apr 15 21:15:01 sunny2 kernel: [ 1886.956365] sd 6:0:0:0: [sdb] Mode
 Sense: 77 00 00 08
 Apr 15 21

Re: open-iscsi created only one disk but missing 2 more

2009-04-16 Thread sundar mahadevan

Thanks for your reply.

But i might sound a little stupid to ask this:

A very basic question:

The hard disks i 'm using is ATA. I believe that open-iscsi works on
scsi devices. Please enlighten me on this.

On Thu, Apr 16, 2009 at 10:08 AM, Mike Christie micha...@cs.wisc.edu wrote:

 sundar mahadevan wrote:
 I tried the same connecting another hard drive of 20 G with 3 logical
 volumes namely: asm 17G , ocr 924M and vote 760M.

 iscsiadm -m node -T iqn.2001-04.com.ubuntu:scsi.disk.vg1.ocr -p 
 192.168.20.22 -l
 iscsiadm -m node -T iqn.2001-04.com.ubuntu:scsi.disk.vg1.vote -p
 192.168.20.22 -l
 iscsiadm -m node -T iqn.2001-04.com.ubuntu:scsi.disk.vg1.asm -p 
 192.168.20.22 -l

 Looks like it only created the first one: ocr

 Here is the log from /var/log/syslog
 Apr 15 21:10:17 sunny2 kernel: [ 1603.409561] Loading iSCSI transport
 class v2.0-870.
 Apr 15 21:10:17 sunny2 kernel: [ 1603.486634] iscsi: registered transport 
 (tcp)
 Apr 15 21:10:18 sunny2 kernel: [ 1603.848719] iscsi: registered transport 
 (iser)
 Apr 15 21:10:18 sunny2 iscsid: iSCSI logger with pid=5912 started!
 Apr 15 21:10:18 sunny2 kernel: [ 1604.408284] scsi2 : iSCSI Initiator
 over TCP/IP
 Apr 15 21:10:19 sunny2 iscsid: transport class version 2.0-870. iscsid
 version 2.0-865
 Apr 15 21:10:19 sunny2 iscsid: iSCSI daemon with pid=5914 started!
 Apr 15 21:10:19 sunny2 iscsid: Could not verify connection 1:2. Dropping 
 event.
 Apr 15 21:10:19 sunny2 iscsid: Could not verify connection 1:2. Dropping 
 event.

 Are you building the open-iscsi tools or are they part of the distro you
 are using?

 Are you also using qla4xxx or just using iscsi_tcp?

 If you are building your own tools make sure if you are using a 64 bit
 kernel then the tools are also compiled as 64 bits.

 Make sure that you only have one set of tools installed. Do a whereis
 iscsid and whereis iscsiadm.

 


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
open-iscsi group.
To post to this group, send email to open-iscsi@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
-~--~~~~--~~--~--~---



Re: open-iscsi created only one disk but missing 2 more

2009-04-16 Thread sundar mahadevan

 Are you building the open-iscsi tools or are they part of the distro you
 are using?

I just used apt-get install open-iscsi on both systems.

 Are you also using qla4xxx or just using iscsi_tcp?

 I dont think i use qla4xxx. I think i use iscsi_tcp.

 If you are building your own tools make sure if you are using a 64 bit
 kernel then the tools are also compiled as 64 bits.

  I'm on a 32 bit system. In that case what is a 64 bit of use to me.

 Make sure that you only have one set of tools installed. Do a whereis
 iscsid and whereis iscsiadm.

whereis iscsid
iscsid: /sbin/iscsid /usr/share/man/man8/iscsid.8.gz
whereis iscsiadm
iscsiadm: /sbin/iscsiadm /usr/share/man/man8/iscsiadm.8.gz

You are using IET right? If so it does not matter what disks you use.
IET can handle it.

No i dont use IET. I use open-iscsi on both systems.

 I tried the same connecting another hard drive of 20 G with 3 logical
 volumes namely: asm 17G , ocr 924M and vote 760M.

 iscsiadm -m node -T iqn.2001-04.com.ubuntu:scsi.disk.vg1.ocr -p 
 192.168.20.22 -l
 iscsiadm -m node -T iqn.2001-04.com.ubuntu:scsi.disk.vg1.vote -p
 192.168.20.22 -l
 iscsiadm -m node -T iqn.2001-04.com.ubuntu:scsi.disk.vg1.asm -p 
 192.168.20.22 -l

 Looks like it only created the first one: ocr

 Here is the log from /var/log/syslog
 Apr 15 21:10:17 sunny2 kernel: [ 1603.409561] Loading iSCSI transport
 class v2.0-870.
 Apr 15 21:10:17 sunny2 kernel: [ 1603.486634] iscsi: registered transport 
 (tcp)
 Apr 15 21:10:18 sunny2 kernel: [ 1603.848719] iscsi: registered transport 
 (iser)
 Apr 15 21:10:18 sunny2 iscsid: iSCSI logger with pid=5912 started!
 Apr 15 21:10:18 sunny2 kernel: [ 1604.408284] scsi2 : iSCSI Initiator
 over TCP/IP
 Apr 15 21:10:19 sunny2 iscsid: transport class version 2.0-870. iscsid
 version 2.0-865
 Apr 15 21:10:19 sunny2 iscsid: iSCSI daemon with pid=5914 started!
 Apr 15 21:10:19 sunny2 iscsid: Could not verify connection 1:2. Dropping 
 event.
 Apr 15 21:10:19 sunny2 iscsid: Could not verify connection 1:2. Dropping 
 event.

 Are you building the open-iscsi tools or are they part of the distro you
 are using?

 Are you also using qla4xxx or just using iscsi_tcp?

 If you are building your own tools make sure if you are using a 64 bit
 kernel then the tools are also compiled as 64 bits.

 Make sure that you only have one set of tools installed. Do a whereis
 iscsid and whereis iscsiadm.

 


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
open-iscsi group.
To post to this group, send email to open-iscsi@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
-~--~~~~--~~--~--~---



Re: open-iscsi created only one disk but missing 2 more

2009-04-16 Thread sundar mahadevan

kernel: 2.6.27-11

IET is your target.
To my understanding IET is iscsi enterprise target which is similar to
open-iscsi in implementing iscsi targets. open-iscsi and IET are
different organisations implementing iscsi. Am i right?



On Thu, Apr 16, 2009 at 10:46 AM, Mike Christie micha...@cs.wisc.edu wrote:

 sundar mahadevan wrote:
 Are you building the open-iscsi tools or are they part of the distro you
 are using?

 I just used apt-get install open-iscsi on both systems.


 What kernel are you using (uname -a)?

 Are you also using qla4xxx or just using iscsi_tcp?

  I dont think i use qla4xxx. I think i use iscsi_tcp.

 If you are building your own tools make sure if you are using a 64 bit
 kernel then the tools are also compiled as 64 bits.

   I'm on a 32 bit system. In that case what is a 64 bit of use to me.

 Make sure that you only have one set of tools installed. Do a whereis
 iscsid and whereis iscsiadm.

 whereis iscsid
 iscsid: /sbin/iscsid /usr/share/man/man8/iscsid.8.gz
 whereis iscsiadm
 iscsiadm: /sbin/iscsiadm /usr/share/man/man8/iscsiadm.8.gz

 You are using IET right? If so it does not matter what disks you use.
 IET can handle it.

 No i dont use IET. I use open-iscsi on both systems.

 IET is your target.

 


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
open-iscsi group.
To post to this group, send email to open-iscsi@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
-~--~~~~--~~--~--~---



Re: open-iscsi created only one disk but missing 2 more

2009-04-16 Thread sundar mahadevan

Could someone enlighten me on this question please:
Do i have to install iscsitarget on system 1 and access it with
open-iscsi(iscsi initiator) from system 2 or
can i have open-iscsi installed on both system 1 and system 2 and get
it working?

On Thu, Apr 16, 2009 at 10:51 AM, sundar mahadevan
sundarmahadeva...@gmail.com wrote:
 kernel: 2.6.27-11

 IET is your target.
 To my understanding IET is iscsi enterprise target which is similar to
 open-iscsi in implementing iscsi targets. open-iscsi and IET are
 different organisations implementing iscsi. Am i right?



 On Thu, Apr 16, 2009 at 10:46 AM, Mike Christie micha...@cs.wisc.edu wrote:

 sundar mahadevan wrote:
 Are you building the open-iscsi tools or are they part of the distro you
 are using?

 I just used apt-get install open-iscsi on both systems.


 What kernel are you using (uname -a)?

 Are you also using qla4xxx or just using iscsi_tcp?

  I dont think i use qla4xxx. I think i use iscsi_tcp.

 If you are building your own tools make sure if you are using a 64 bit
 kernel then the tools are also compiled as 64 bits.

   I'm on a 32 bit system. In that case what is a 64 bit of use to me.

 Make sure that you only have one set of tools installed. Do a whereis
 iscsid and whereis iscsiadm.

 whereis iscsid
 iscsid: /sbin/iscsid /usr/share/man/man8/iscsid.8.gz
 whereis iscsiadm
 iscsiadm: /sbin/iscsiadm /usr/share/man/man8/iscsiadm.8.gz

 You are using IET right? If so it does not matter what disks you use.
 IET can handle it.

 No i dont use IET. I use open-iscsi on both systems.

 IET is your target.

 



--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
open-iscsi group.
To post to this group, send email to open-iscsi@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
-~--~~~~--~~--~--~---



Re: open-iscsi created only one disk but missing 2 more

2009-04-15 Thread sundar mahadevan

Could someone please help me with this issue.

On Wed, Apr 15, 2009 at 11:41 AM, sundar mahadevan
sundarmahadeva...@gmail.com wrote:
 Hi,
 I'm a newbie trying to setup open-iscsi on ubuntu 8.10(kernel 2.6.27-11).

 I created 3 logical volumes(asm : 37G, ocr: 2G and vote 1G) under a
 volume group vg1 comprising of 3 physical volumes (totalling 40G)

 Here are my commands from client side:

    sudo iscsiadm -m discovery -t st -p 192.168.20.22

 lists:
 192.168.20.22:3260,1 iqn.2001-04.com.ezhome:scsi.disk.vg1.asm
 192.168.20.22:3260,1 iqn.2001-04.com.ezhome:scsi.disk.vg1.ocr
 192.168.20.22:3260,1 iqn.2001-04.com.ezhome:scsi.disk.vg1.vote

    sudo /etc/init.d/open-iscsi restart

    sudo iscsiadm -m node -T iqn.2001-04.com.ezhome:scsi.disk.vg1.asm
 -p 192.168.20.22 -o update -n node.conn[0].startup -v automatic

    sudo iscsiadm -m node -T iqn.2001-04.com.ezhome:scsi.disk.vg1.ocr
 -p 192.168.20.22 -o update -n node.conn[0].startup -v automatic

    sudo iscsiadm -m node -T iqn.2001-04.com.ezhome:scsi.disk.vg1.vote
 -p 192.168.20.22 -o update -n node.conn[0].startup -v automatic

    sudo /etc/init.d/open-iscsi restart

 fdisk -l and dmesg

 1) list a new drive /dev/sdb of size 39.7 GB but there should be 2
 more drives and the size of /dev/sdb is surprising because there are
 no drives of size 39.7G

 2) What am i missing here for other 2 drives to be visible.

 3) Changes made to /etc/ietd.conf and then /etc/init.d/open-iscsi
 restart does not get reflected. I have to reboot the system to notice
 the changes. Any ideas?

 4) am i supposed to use /etc/init.d/iscsitarget stop/restart to stop
 and restart iscsitargets?

 Thanks in advance.


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
open-iscsi group.
To post to this group, send email to open-iscsi@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
-~--~~~~--~~--~--~---



Re: open-iscsi created only one disk but missing 2 more

2009-04-15 Thread sundar mahadevan

I tried the same connecting another hard drive of 20 G with 3 logical
volumes namely: asm 17G , ocr 924M and vote 760M.

iscsiadm -m node -T iqn.2001-04.com.ubuntu:scsi.disk.vg1.ocr -p 192.168.20.22 -l
iscsiadm -m node -T iqn.2001-04.com.ubuntu:scsi.disk.vg1.vote -p
192.168.20.22 -l
iscsiadm -m node -T iqn.2001-04.com.ubuntu:scsi.disk.vg1.asm -p 192.168.20.22 -l

Looks like it only created the first one: ocr

Here is the log from /var/log/syslog
Apr 15 21:10:17 sunny2 kernel: [ 1603.409561] Loading iSCSI transport
class v2.0-870.
Apr 15 21:10:17 sunny2 kernel: [ 1603.486634] iscsi: registered transport (tcp)
Apr 15 21:10:18 sunny2 kernel: [ 1603.848719] iscsi: registered transport (iser)
Apr 15 21:10:18 sunny2 iscsid: iSCSI logger with pid=5912 started!
Apr 15 21:10:18 sunny2 kernel: [ 1604.408284] scsi2 : iSCSI Initiator
over TCP/IP
Apr 15 21:10:19 sunny2 iscsid: transport class version 2.0-870. iscsid
version 2.0-865
Apr 15 21:10:19 sunny2 iscsid: iSCSI daemon with pid=5914 started!
Apr 15 21:10:19 sunny2 iscsid: Could not verify connection 1:2. Dropping event.
Apr 15 21:10:19 sunny2 iscsid: Could not verify connection 1:2. Dropping event.
Apr 15 21:10:20 sunny2 kernel: [ 1606.064265] scsi3 : iSCSI Initiator
over TCP/IP
Apr 15 21:10:21 sunny2 iscsid: Could not verify connection 2:3. Dropping event.
Apr 15 21:10:21 sunny2 iscsid: Could not verify connection 2:3. Dropping event.
Apr 15 21:10:21 sunny2 kernel: [ 1607.592257] scsi4 : iSCSI Initiator
over TCP/IP
Apr 15 21:10:22 sunny2 iscsid: Could not verify connection 3:4. Dropping event.
Apr 15 21:10:22 sunny2 iscsid: Could not verify connection 3:4. Dropping event.
Apr 15 21:10:23 sunny2 kernel: [ 1609.120249] scsi5 : iSCSI Initiator
over TCP/IP
Apr 15 21:10:24 sunny2 iscsid: Could not verify connection 4:5. Dropping event.
Apr 15 21:10:24 sunny2 iscsid: Could not verify connection 4:5. Dropping event.
Apr 15 21:15:00 sunny2 kernel: [ 1886.664257] scsi6 : iSCSI Initiator
over TCP/IP
Apr 15 21:15:01 sunny2 iscsid: Could not verify connection 5:6. Dropping event.
Apr 15 21:15:01 sunny2 kernel: [ 1886.946886] scsi 6:0:0:0:
Direct-Access IET  VIRTUAL-DISK 0PQ: 0 ANSI: 4
Apr 15 21:15:01 sunny2 kernel: [ 1886.952267] sd 6:0:0:0: [sdb]
1892352 512-byte hardware sectors (969 MB)
Apr 15 21:15:01 sunny2 kernel: [ 1886.956338] sd 6:0:0:0: [sdb] Write
Protect is off
Apr 15 21:15:01 sunny2 kernel: [ 1886.956365] sd 6:0:0:0: [sdb] Mode
Sense: 77 00 00 08
Apr 15 21:15:01 sunny2 kernel: [ 1886.964101] sd 6:0:0:0: [sdb] Write
cache: disabled, read cache: enabled, doesn't support DPO or FUA
Apr 15 21:15:01 sunny2 kernel: [ 1886.976089] sd 6:0:0:0: [sdb]
1892352 512-byte hardware sectors (969 MB)
Apr 15 21:15:01 sunny2 kernel: [ 1886.986197] sd 6:0:0:0: [sdb] Write
Protect is off
Apr 15 21:15:01 sunny2 kernel: [ 1886.986228] sd 6:0:0:0: [sdb] Mode
Sense: 77 00 00 08
Apr 15 21:15:01 sunny2 kernel: [ 1887.82] sd 6:0:0:0: [sdb] Write
cache: disabled, read cache: enabled, doesn't support DPO or FUA
Apr 15 21:15:01 sunny2 kernel: [ 1887.002741]  sdb: unknown partition table
Apr 15 21:15:01 sunny2 kernel: [ 1887.042501] sd 6:0:0:0: [sdb]
Attached SCSI disk
Apr 15 21:15:01 sunny2 kernel: [ 1887.043773] sd 6:0:0:0: Attached
scsi generic sg1 type 0
Apr 15 21:15:02 sunny2 iscsid: connection5:0 is operational now
Apr 15 21:15:20 sunny2 iscsid: Could not get host for sid 5.
Apr 15 21:15:20 sunny2 iscsid: could not get host_no for session 6.
Apr 15 21:15:20 sunny2 iscsid: could not find session info for session5
Apr 15 21:15:20 sunny2 iscsid: session
[iqn.2001-04.com.ubuntu:scsi.disk.vg1.vote,192.168.20.22,3260] already
running.
Apr 15 21:15:28 sunny2 iscsid: Nop-out timedout after 15 seconds on
connection 5:0 state (3). Dropping session.
Apr 15 21:15:28 sunny2 iscsid: connection5:0 is operational after
recovery (1 attempts)
Apr 15 21:15:33 sunny2 iscsid: Could not get host for sid 5.
Apr 15 21:15:33 sunny2 iscsid: could not get host_no for session 6.
Apr 15 21:15:33 sunny2 iscsid: could not find session info for session5
Apr 15 21:15:33 sunny2 iscsid: session
[iqn.2001-04.com.ubuntu:scsi.disk.vg1.asm,192.168.20.22,3260] already
running.
Apr 15 21:15:54 sunny2 iscsid: Nop-out timedout after 15 seconds on
connection 5:0 state (3). Dropping session.
Apr 15 21:15:54 sunny2 iscsid: connection5:0 is operational after
recovery (1 attempts)

Could someone help me please. I have been battling to figure this out
for a while. It really is frustrating that nothing works. Thanks in
advance.

On Wed, Apr 15, 2009 at 3:58 PM, sundar mahadevan
sundarmahadeva...@gmail.com wrote:
 Could someone please help me with this issue.

 On Wed, Apr 15, 2009 at 11:41 AM, sundar mahadevan
 sundarmahadeva...@gmail.com wrote:
 Hi,
 I'm a newbie trying to setup open-iscsi on ubuntu 8.10(kernel 2.6.27-11).

 I created 3 logical volumes(asm : 37G, ocr: 2G and vote 1G) under a
 volume group vg1 comprising of 3 physical volumes (totalling 40G)

 Here are my commands from client side:

    sudo