iscsid died and kernel module screwed?

2009-10-01 Thread Kevin Ye
Hi there,

We hit a iscsid die case. use ps -ef|grep iscsid, we only saw one iscsid
process.

Unfortunately, we didn't enable debug log so there are not many logs
available. We looked at the iscsid log it states that it received some
kernel reported error. Also, in the kernel log, there is OOP complaints.

 After that, we used open-iscsi init script to restart, but the kernel
modules were not been able to removed. We issue iscsiadm -m session, it
gives:
 r...@swe_1_ser_2:~# iscsiadm --mode session
tcp: [17] []:-1,1 \ufffd\ufffd?\ufffd|0\ufffdHYw

The iscsiadm --mode session -P 3 hangs:

r...@swe_1_ser_2:~# iscsiadm --mode session -P 3
iSCSI Transport Class version 2.0-870
iscsiadm version 2.0-870
Target: \ufffd\ufffd?\u04cbA\ufffd\ufffd\ufffd?
Current Portal: []:-1,1
Persistent Portal: []:-1,1
**
Interface:
**
Iface Name: .bss
Iface Transport: tcp
Iface Initiatorname: iqn.1993-08.org.debian:01:f0de76895ed6
Iface IPaddress: [192.168.1.99]
Iface HWaddress: default
Iface Netdev: default
SID: 17


iscsid log:

Sep 29 13:00:05 swe_1_ser_2 iscsid: Kernel reported iSCSI connection 16:0
error (1011) state (3)
Sep 29 13:00:05 swe_1_ser_2 iscsid: Kernel reported iSCSI connection 17:0
error (1011) state (3)
 Sep 29 13:00:10 swe_1_ser_2 iscsid: connect failed (111)
Sep 29 13:00:10 swe_1_ser_2 iscsid: connect failed (111)
Sep 29 13:00:17 swe_1_ser_2 iscsid: connect failed (111)
Sep 29 13:00:17 swe_1_ser_2 iscsid: connect failed (111)
Sep 29 13:00:23 swe_1_ser_2 iscsid: connect failed (111)
Sep 29 13:00:23 swe_1_ser_2 iscsid: connect failed (111)

kernel log:
Sep 29 13:00:05 swe_1_ser_2 kernel: [ 8459.978988]  connection16:0: ping
timeout of 15 secs expired, last rx 2035865, last ping 2038365, now 2042115
Sep 29 13:00:05 swe_1_ser_2 kernel: [ 8459.979351]  connection16:0: detected
conn error (1011)
Sep 29 13:00:05 swe_1_ser_2 kernel: [ 8460.094535]  connection17:0: ping
timeout of 15 secs expired, last rx 2035894, last ping 2038394, now 2042144
Sep 29 13:00:05 swe_1_ser_2 kernel: [ 8460.094733]  connection17:0: detected
conn error (1011)
Sep 29 13:02:05 swe_1_ser_2 kernel: [ 8580.129711]  session16: session
recovery timed out after 120 secs
Sep 29 13:02:05 swe_1_ser_2 kernel: [ 8580.129860]  session17: session
recovery timed out after 120 secs
Sep 29 13:02:05 swe_1_ser_2 kernel: [ 8580.133734] sd 373:0:0:75: [sdd]
Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK,SUGGEST_OK
Sep 29 13:02:05 swe_1_ser_2 kernel: [ 8580.133747] end_request: I/O error,
dev sdd, sector 1638144
Sep 29 13:02:05 swe_1_ser_2 kernel: [ 8580.133753] Buffer I/O error on
device sdd, logical block 204768
Sep 29 13:02:05 swe_1_ser_2 kernel: [ 8580.133873] sd 374:0:0:78: [sde]
Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK,SUGGEST_OK
Sep 29 13:02:05 swe_1_ser_2 kernel: [ 8580.133878] end_request: I/O error,
dev sde, sector 24
Sep 29 13:02:05 swe_1_ser_2 kernel: [ 8580.133881] Buffer I/O error on
device sde, logical block 3
Sep 29 13:02:05 swe_1_ser_2 kernel: [ 8580.134087] sd 373:0:0:75: [sdd]
Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK,SUGGEST_OK
Sep 29 13:02:05 swe_1_ser_2 kernel: [ 8580.134093] end_request: I/O error,
dev sdd, sector 1638144
Sep 29 13:02:05 swe_1_ser_2 kernel: [ 8580.134097] Buffer I/O error on
device sdd, logical block 204768
Sep 29 13:02:23 swe_1_ser_2 kernel: [ 8597.655094] sd 374:0:0:78: [sde]
Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK,SUGGEST_OK
Sep 29 13:02:23 swe_1_ser_2 kernel: [ 8597.655101] end_request: I/O error,
dev sde, sector 1638144
Sep 29 13:02:23 swe_1_ser_2 kernel: [ 8597.655349] sd 374:0:0:78: [sde]
Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK,SUGGEST_OK
Sep 29 13:02:23 swe_1_ser_2 kernel: [ 8597.655356] end_request: I/O error,
dev sde, sector 0
Sep 29 13:02:25 swe_1_ser_2 kernel: [ 8600.193745] BUG: unable to handle
kernel NULL pointer dereference at virtual address 0060
Sep 29 13:02:25 swe_1_ser_2 kernel: [ 8600.193951] printing eip: e08ce12a
*pde = 
Sep 29 13:02:25 swe_1_ser_2 kernel: [ 8600.194234] Oops:  [#1] SMP
Sep 29 13:02:25 swe_1_ser_2 kernel: [ 8600.194407] Modules linked in:
ipt_REJECT iscsi_tcp libiscsi scsi_transport_iscsi iscsi_trgt crc32c
libcrc32c nls_iso8859_1 nls_cp437 vfat fat vmmemctl cpufreq_conservative
cpufreq_ondemand cpufreq_userspace cpufreq_stats freq_table
cpufreq_powersave sbs video output sbshc dock battery iptable_filter
ip_tables x_tables vmhgfs lp loop ipv6 container serio_raw ac i2c_piix4
button intel_agp i2c_core agpgart shpchp pci_hotplug parport_pc parport
evdev psmouse pcspkr ext3 jbd mbcache sr_mod cdrom pata_acpi ata_generic sg
sd_mod floppy pcnet32 ata_piix mii mptspi mptscsih mptbase
scsi_transport_spi libata scsi_mod raid10 raid456 async_xor async_memcpy
async_tx xor raid1 raid0 multipath linear md_mod dm_mirror dm_snapshot
dm_mod thermal processor fan fbcon tileblit font bitblit softcursor fuse
vmxnet
Sep 29 13:02:25 

Re: iscsid died and kernel module screwed?

2009-10-01 Thread Kevin Ye
We use 2.0-870.3. The kernel is Ubuntu 8.04 with kernel 2.6.24-24.

We get the open-iscsi modules and tools from open-iscsi.org.

Thanks.
Kevin

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


 On 09/30/2009 03:27 PM, Kevin Ye wrote:
  Sep 29 13:02:25 swe_1_ser_2 kernel: [ 8600.195515]
  Sep 29 13:02:25 swe_1_ser_2 kernel: [ 8600.195623] Pid: 5839, comm:
 iscsid
  Not tainted (2.6.24-24-generic #1)
  Sep 29 13:02:25 swe_1_ser_2 kernel: [ 8600.195719] EIP: 0060:[e08ce12a]
  EFLAGS: 00010202 CPU: 0
  Sep 29 13:02:25 swe_1_ser_2 kernel: [ 8600.196041] EIP is at
  spi_device_match+0x1a/0x60 [scsi_transport_spi]

 This is a little strange. What version of open-iscsi are you using?
 Where did you get the kernel or what distro is this? Are you using the
 distro's iscsi modules and tools or are they from open-iscsi.org?

 


--~--~-~--~~~---~--~~
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
-~--~~~~--~~--~--~---