Hi Carlopmart,
carlopmart wrote:
carlopmart wrote:
carlopmart wrote:
Hi all,
I having problems using iscsi initiator under opensolaris. I can to
connect to two iscsi targets (one Solaris 10u8 based and another
opensolaris 2009.06) without problems. I can create zfs volums,
erase files, create files, etc ... all works ok. But problems
appears when I try to shutdown or reboot this opensolaris
workstation, then these errors appears:
Nov 11 16:01:51 mordor iscsi: [ID 213721 kern.notice] NOTICE: iscsi
session(20) - session logout failed (1)
Nov 11 16:01:51 mordor iscsi: [ID 213721 kern.notice] NOTICE: iscsi
session(17) - session logout failed (1)
Nov 11 16:01:51 mordor iscsi: [ID 213721 kern.notice] NOTICE: iscsi
session(9) - session logout failed (1)
Nov 11 16:01:51 mordor iscsi: [ID 213721 kern.notice] NOTICE: iscsi
session(6) - session logout failed (1)
Nov 11 16:01:51 mordor iscsi: [ID 882656 kern.notice] NOTICE: iscsi
discovery failure - StaticTargets method is not enabled
Nov 11 16:01:51 mordor iscsi: [ID 299153 kern.notice] NOTICE: iscsi
discovery failure - iSNS method is not enabled
At this moment I need to wait between four or five minutes until an
iscsi initiator error appears:
Nov 11 16:44:16/3: svc:/network/iscsi/initiator:default: Method or
service exit timed out. Killing contract 35.
Nov 11 16:44:16/197: network/iscsi/initiator:default failed:
transitioned to maintenance (see 'svcs -xv' for details)
then workstation reboots or stops ... When this workstation starts
up, all iscsi disks are reconnected without problems and under dmesg
any error appears.
On network-iscsi-initiator:default.log exists these entries:
bash-3.00# cat network-iscsi-initiator:default.log
[ Nov 11 15:44:59 Enabled. ]
[ Nov 11 15:44:59 Rereading configuration. ]
[ Nov 11 15:45:00 Executing start method ("/lib/svc/method/iscsid") ]
[ Nov 11 15:45:00 Method "start" exited with status 0 ]
[ Nov 11 15:51:57 Stopping because service disabled. ]
[ Nov 11 15:51:57 Executing stop method (:kill) ]
[ Nov 11 15:53:00 Enabled. ]
[ Nov 11 15:53:06 Executing start method ("/lib/svc/method/iscsid") ]
[ Nov 11 15:53:07 Method "start" exited with status 0 ]
[ Nov 11 16:01:51 Stopping because service disabled. ]
[ Nov 11 16:01:51 Executing stop method (:kill) ]
[ Nov 11 16:11:51 Method or service exit timed out. Killing
contract 33 ]
[ Nov 11 16:12:50 Enabled. ]
[ Nov 11 16:12:58 Executing start method ("/lib/svc/method/iscsid") ]
[ Nov 11 16:13:01 Method "start" exited with status 0 ]
iscsi initiator discovery options are configrued like this:
bash-3.00# iscsiadm list discovery
Discovery:
Static: disabled
Send Targets: enabled
iSNS: disabled
I have tested this configuration on a solaris 10u8 workstation and
problems continues. On the other side, I haver several linux and
windows 2008 clients connected to these targets without problems:
they can to connect, disconnect and reconnect without issues.
Where is the problem?? Do I need to modify some iscsi initiator
param??
Many thanks.
Uhmm ... More info. I have seen this messages in /var/log/syslog:
Nov 11 22:05:26 mordor iscsi: [ID 240218 kern.notice] NOTICE: iscsi
session(9)
iqn.1986-03.com.sun:02:7d7d0a9b-a6d9-eef4-b9d5-8be691d790e7.iopsysvol01
online
Nov 11 22:05:26 mordor scsi: [ID 799468 kern.info] sd9 at scsi_vhci0:
name g600144f04afb2687000050562d703000, bus address
g600144f04afb2687000050562d703000
Nov 11 22:05:26 mordor genunix: [ID 936769 kern.info] sd9 is
/scsi_vhci/d...@g600144f04afb2687000050562d703000
Nov 11 22:05:26 mordor genunix: [ID 408114 kern.info]
/scsi_vhci/d...@g600144f04afb2687000050562d703000 (sd9) online
Nov 11 22:05:26 mordor genunix: [ID 834635 kern.info]
/scsi_vhci/d...@g600144f04afb2687000050562d703000 (sd9) multipath
status: degraded, path /iscsi (iscsi0) to target address:
0000iqn.1986-03.com.sun:02:7d7d0a9b-a6d9-eef4-b9d5-8be691d790e7.iopsysvol010001,0
is online Load balancing: round-robin
Nov 11 22:05:26 mordor iscsi: [ID 240218 kern.notice] NOTICE: iscsi
session(6)
iqn.1986-03.com.sun:02:1d062de4-d061-4183-8d5e-aa2eb9628f4d.idatavol01
online
Nov 11 22:05:26 mordor scsi: [ID 799468 kern.info] sd10 at
scsi_vhci0: name g600144f04afb26c5000050562d703000, bus address
g600144f04afb26c5000050562d703000
Nov 11 22:05:26 mordor genunix: [ID 936769 kern.info] sd10 is
/scsi_vhci/d...@g600144f04afb26c5000050562d703000
Nov 11 22:05:26 mordor genunix: [ID 408114 kern.info]
/scsi_vhci/d...@g600144f04afb26c5000050562d703000 (sd10) online
Nov 11 22:05:26 mordor genunix: [ID 834635 kern.info]
/scsi_vhci/d...@g600144f04afb26c5000050562d703000 (sd10) multipath
status: degraded, path /iscsi (iscsi0) to target address:
0000iqn.1986-03.com.sun:02:1d062de4-d061-4183-8d5e-aa2eb9628f4d.idatavol010001,0
is online Load balancing: round-robin
Nov 11 22:07:46 mordor iscsi: [ID 240218 kern.notice] NOTICE: iscsi
session(22)
iqn.1986-03.com.sun:02:4fb10b36-d903-4c25-cee8-cbd6bfde20bd.iopsysvol02
online
Nov 11 22:07:47 mordor pseudo: [ID 129642 kern.info] pseudo-device:
devinfo0
Nov 11 22:07:47 mordor genunix: [ID 936769 kern.info] devinfo0 is
/pseudo/devi...@0
Nov 11 22:07:47 mordor scsi: [ID 799468 kern.info] sd11 at
scsi_vhci0: name g600144f04afb27c4000050562d107000, bus address
g600144f04afb27c4000050562d107000
Nov 11 22:07:47 mordor genunix: [ID 936769 kern.info] sd11 is
/scsi_vhci/d...@g600144f04afb27c4000050562d107000
Nov 11 22:07:47 mordor genunix: [ID 408114 kern.info]
/scsi_vhci/d...@g600144f04afb27c4000050562d107000 (sd11) online
Nov 11 22:07:47 mordor genunix: [ID 834635 kern.info]
/scsi_vhci/d...@g600144f04afb27c4000050562d107000 (sd11) multipath
status: degraded, path /iscsi (iscsi0) to target address:
0000iqn.1986-03.com.sun:02:4fb10b36-d903-4c25-cee8-cbd6bfde20bd.iopsysvol020001,0
is online Load balancing: round-robin
Nov 11 22:07:47 mordor iscsi: [ID 240218 kern.notice] NOTICE: iscsi
session(19)
iqn.1986-03.com.sun:02:76cc59a6-d404-e58e-9e26-f5ef64b226f2.idatavol02
online
Nov 11 22:07:48 mordor scsi: [ID 799468 kern.info] sd12 at
scsi_vhci0: name g600144f04afb27c5000050562d107000, bus address
g600144f04afb27c5000050562d107000
Nov 11 22:07:48 mordor genunix: [ID 936769 kern.info] sd12 is
/scsi_vhci/d...@g600144f04afb27c5000050562d107000
Nov 11 22:07:48 mordor genunix: [ID 408114 kern.info]
/scsi_vhci/d...@g600144f04afb27c5000050562d107000 (sd12) online
Nov 11 22:07:48 mordor genunix: [ID 834635 kern.info]
/scsi_vhci/d...@g600144f04afb27c5000050562d107000 (sd12) multipath
status: degraded, path /iscsi (iscsi0) to target address:
0000iqn.1986-03.com.sun:02:76cc59a6-d404-e58e-9e26-f5ef64b226f2.idatavol020001,0
is online Load balancing: round-robin
round-robin?? multipath?? why?? They are different targets with
different volume names ...
Ok, I think it is a mirror problem. What i am trying to do is to use
this opensolaris to mirror disks allocated on these two targets, like
this:
pool: idatapool
state: ONLINE
scrub: none requested
config:
NAME STATE READ
WRITE CKSUM
idatapool ONLINE 0
0 0
mirror ONLINE 0
0 0
c0t600144F04AFB26C5000050562D703000d0 ONLINE 0
0 0
c0t600144F04AFB27C5000050562D107000d0 ONLINE 0
0 0
errors: No known data errors
pool: iopsysvol
state: ONLINE
scrub: none requested
config:
NAME STATE READ
WRITE CKSUM
iopsysvol ONLINE 0
0 0
mirror ONLINE 0
0 0
c0t600144F04AFB2687000050562D703000d0 ONLINE 0
0 0
c0t600144F04AFB27C4000050562D107000d0 ONLINE 0
0 0
errors: No known data errors
Could that be a problem?
There seems no issue. Multipathing is enabled by default with
round-robin even there is only one path, however it will appear
'degraded' as you may already have seen in the console output. Also,
this behavior is irrelevant to how the zpool is configured.
Best regards,
Jack
_______________________________________________
opensolaris-discuss mailing list
[email protected]
