On 07/26/2010 10:37 PM, Anil wrote:
What I meant is when we use BIO_RW_BARRIER flag along with other
flags, then, we dont see iscsi error messages that frequently. But
using that flag is hitting performance, as merging is not allowed for
those bios.
With bio rw barrier are you seeing the messages below?
Is the kernel you are using the newest one for SLES 10? What is the
current sp version for SLES 10?
Do you see some debug files
/sys/module/iscsi_tcp/parameters/debug_iscsi_tcp
/sys/module/libiscsi_tcp/parameters/debug_libiscsi_tcp
/sys/module/libiscsi/parameters/debug_libiscsi_conn
/sys/module/libiscsi/parameters/debug_libiscsi_session
/sys/module/libiscsi/parameters/debug_libiscsi_eh
If you do, could you do a echo 1 to each one like this:
echo 1 > /sys/module/iscsi_tcp/parameters/debug_iscsi_tcp
Jul 26 14:32:46 DS-1-29-SLES10-SP2-64bit-Xen kernel: Locate returning
SUCCESS
Jul 26 14:32:46 DS-1-29-SLES10-SP2-64bit-Xen kernel: iscsi: received
itt 0 expected session age (0)
Jul 26 14:32:46 DS-1-29-SLES10-SP2-64bit-Xen kernel: connection1:0:
iscsi: detected conn error (1011)
Jul 26 14:32:46 DS-1-29-SLES10-SP2-64bit-Xen kernel: Locate returning
SUCCESS
Jul 26 14:32:46 DS-1-29-SLES10-SP2-64bit-Xen kernel: Locate returning
SUCCESS
Jul 26 14:32:47 DS-1-29-SLES10-SP2-64bit-Xen iscsid: Kernel reported
iSCSI connection 1:0 error (1011) state (3)
Jul 26 14:32:51 DS-1-29-SLES10-SP2-64bit-Xen kernel: iscsi: received
itt 0 expected session age (0)
Jul 26 14:32:51 DS-1-29-SLES10-SP2-64bit-Xen kernel: connection1:0:
iscsi: detected conn error (1011)
Jul 26 14:32:51 DS-1-29-SLES10-SP2-64bit-Xen iscsid: connection1:0 is
operational after recovery (1 attempts)
Jul 26 14:32:52 DS-1-29-SLES10-SP2-64bit-Xen iscsid: Kernel reported
iSCSI connection 1:0 error (1011) state (3)
Jul 26 14:32:55 DS-1-29-SLES10-SP2-64bit-Xen iscsid: connection1:0 is
operational after recovery (1 attempts)
Jul 26 14:32:56 DS-1-29-SLES10-SP2-64bit-Xen kernel: iscsi: received
itt 0 expected session age (0)
Jul 26 14:32:56 DS-1-29-SLES10-SP2-64bit-Xen kernel: connection1:0:
iscsi: detected conn error (1011)
Jul 26 14:32:56 DS-1-29-SLES10-SP2-64bit-Xen iscsid: Kernel reported
iSCSI connection 1:0 error (1011) state (3)
Jul 26 14:33:00 DS-1-29-SLES10-SP2-64bit-Xen iscsid: connection1:0 is
operational after recovery (1 attempts)
Jul 26 14:33:00 DS-1-29-SLES10-SP2-64bit-Xen kernel: iscsi: dropping
ctask with itt 0x0
Jul 26 14:33:00 DS-1-29-SLES10-SP2-64bit-Xen kernel: connection1:0:
iscsi: detected conn error (1011)
Jul 26 14:33:01 DS-1-29-SLES10-SP2-64bit-Xen iscsid: Kernel reported
iSCSI connection 1:0 error (1011) state (3)
Jul 26 14:33:05 DS-1-29-SLES10-SP2-64bit-Xen iscsid: connection1:0 is
operational after recovery (1 attempts)
Jul 26 14:33:05 DS-1-29-SLES10-SP2-64bit-Xen kernel: iscsi: received
itt 0 expected session age (0)
Jul 26 14:33:05 DS-1-29-SLES10-SP2-64bit-Xen kernel: connection1:0:
iscsi: detected conn error (1011)
Jul 26 14:33:06 DS-1-29-SLES10-SP2-64bit-Xen iscsid: Kernel reported
iSCSI connection 1:0 error (1011) state (3)
Jul 26 14:33:10 DS-1-29-SLES10-SP2-64bit-Xen kernel: iscsi: received
itt 0 expected session age (0)
Jul 26 14:33:10 DS-1-29-SLES10-SP2-64bit-Xen kernel: connection1:0:
iscsi: detected conn error (1011)
Jul 26 14:33:10 DS-1-29-SLES10-SP2-64bit-Xen iscsid: connection1:0 is
operational after recovery (1 attempts)
Jul 26 14:33:11 DS-1-29-SLES10-SP2-64bit-Xen iscsid: Kernel reported
iSCSI connection 1:0 error (1011) state (3)
Jul 26 14:33:14 DS-1-29-SLES10-SP2-64bit-Xen iscsid: connection1:0 is
operational after recovery (1 attempts)
Jul 26 14:33:15 DS-1-29-SLES10-SP2-64bit-Xen kernel: iscsi: received
itt 0 expected session age (0)
Jul 26 14:33:15 DS-1-29-SLES10-SP2-64bit-Xen kernel: connection1:0:
iscsi: detected conn error (1011)
Jul 26 14:33:15 DS-1-29-SLES10-SP2-64bit-Xen iscsid: Kernel reported
iSCSI connection 1:0 error (1011) state (3)
Jul 26 14:33:19 DS-1-29-SLES10-SP2-64bit-Xen iscsid: connection1:0 is
operational after recovery (1 attempts)
Jul 26 14:33:19 DS-1-29-SLES10-SP2-64bit-Xen kernel: iscsi: received
itt 0 expected session age (0)
Jul 26 14:33:19 DS-1-29-SLES10-SP2-64bit-Xen kernel: connection1:0:
iscsi: detected conn error (1011)
Jul 26 14:33:20 DS-1-29-SLES10-SP2-64bit-Xen iscsid: Kernel reported
iSCSI connection 1:0 error (1011) state (3)
Jul 26 14:41:44 DS-1-29-SLES10-SP2-64bit-Xen iscsid: Kernel reported
iSCSI connection 1:0 error (1011) state (3)
Jul 26 14:41:48 DS-1-29-SLES10-SP2-64bit-Xen iscsid: connection1:0 is
operational after recovery (1 attempts)
Jul 26 14:41:49 DS-1-29-SLES10-SP2-64bit-Xen kernel: iscsi: received
itt 0 expected session age (0)
Jul 26 14:41:49 DS-1-29-SLES10-SP2-64bit-Xen kernel: connection1:0:
iscsi: detected conn error (1011)
Jul 26 14:41:50 DS-1-29-SLES10-SP2-64bit-Xen iscsid: Kernel reported
iSCSI connection 1:0 error (1011) state (3)
Jul 26 14:41:51 DS-1-29-SLES10-SP2-64bit-Xen agetty[12411]: /dev/xvc0:
No such file or directory
Jul 26 14:41:53 DS-1-29-SLES10-SP2-64bit-Xen iscsid: connection1:0 is
operational after recovery (1 attempts)
Jul 26 14:41:53 DS-1-29-SLES10-SP2-64bit-Xen kernel: iscsi: received
itt 0 expected session age (0)
Jul 26 14:41:53 DS-1-29-SLES10-SP2-64bit-Xen kernel: connection1:0:
iscsi: detected conn error (1011)
Jul 26 14:41:53 DS-1-29-SLES10-SP2-64bit-Xen kernel: Failed to inquiry
bdev(8,64) disk:sde
Jul 26 14:41:54 DS-1-29-SLES10-SP2-64bit-Xen iscsid: Kernel reported
iSCSI connection 1:0 error (1011) state (3)
Jul 26 14:41:58 DS-1-29-SLES10-SP2-64bit-Xen iscsid: connection1:0 is
operational after recovery (1 attempts)
Jul 26 14:41:58 DS-1-29-SLES10-SP2-64bit-Xen kernel: Unable to handle
kernel NULL pointer dereference at 0000000000000000 RIP:
Jul 26 14:41:58 DS-1-29-SLES10-SP2-64bit-Xen kernel:
<0000000000000000>{_stext+2146431224}
Jul 26 14:41:58 DS-1-29-SLES10-SP2-64bit-Xen kernel: PGD 3bbb7067 PUD
3ffed067 PMD 0
Jul 26 14:41:58 DS-1-29-SLES10-SP2-64bit-Xen kernel: Oops: 0010 [1]
SMP
Jul 26 14:41:58 DS-1-29-SLES10-SP2-64bit-Xen kernel: last sysfs file: /
devices/platform/host0/session1/target0:0:0/0:0:0:0/state
Jul 26 14:41:58 DS-1-29-SLES10-SP2-64bit-Xen kernel: CPU 0
Jul 26 14:41:58 DS-1-29-SLES10-SP2-64bit-Xen kernel: Modules linked
in: ext3 jbd dsf sg sd_mod crc32c libcrc32c iscsi_tcp libiscsi
scsi_transport_iscsi scsi_mod apparmor loop dm_mod reiserfs xennet edd
processor xenblk
Jul 26 14:41:58 DS-1-29-SLES10-SP2-64bit-Xen kernel: Pid: 4532, comm:
scsi_eh_0 Tainted: G U 2.6.16.60-0.39.3-xen #1
Jul 26 14:41:58 DS-1-29-SLES10-SP2-64bit-Xen kernel: RIP: e030:
[<0000000000000000>]<0000000000000000>{_stext+2146431224}RSP:
e02b:ffff88002d8c1e98 EFLAGS: 00010297
Jul 26 14:41:58 DS-1-29-SLES10-SP2-64bit-Xen kernel: RAX:
0000000000000000 RBX: ffff8800382c4980 RCX: ffff88002d8c1ec0
Jul 26 14:41:58 DS-1-29-SLES10-SP2-64bit-Xen kernel: RDX:
ffffffffff5f9000 RSI: 0000000000000000 RDI: ffff8800382c4980
Jul 26 14:41:58 DS-1-29-SLES10-SP2-64bit-Xen kernel: RBP:
ffff88002d8c1ec0 R08: ffff88002d8c0000 R09: 0000000000000000
Jul 26 14:41:58 DS-1-29-SLES10-SP2-64bit-Xen kernel: R10:
000000010026dfd2 R11: 0000000000000000 R12: ffff88002d8c1ea8
Jul 26 14:41:58 DS-1-29-SLES10-SP2-64bit-Xen kernel: R13:
ffff88003478f868 R14: ffffffff80142c5d R15: 0000000000000000
Jul 26 14:41:58 DS-1-29-SLES10-SP2-64bit-Xen kernel: FS:
00002b378ca966d0(0000) GS:ffffffff803ba000(0000) knlGS:
0000000000000000
Jul 26 14:41:58 DS-1-29-SLES10-SP2-64bit-Xen kernel: CS: e033 DS:
0000 ES: 0000
Jul 26 14:41:58 DS-1-29-SLES10-SP2-64bit-Xen kernel: Process scsi_eh_0
(pid: 4532, threadinfo ffff88002d8c0000, task ffff88003e8da080)
Jul 26 14:41:58 DS-1-29-SLES10-SP2-64bit-Xen kernel: Stack:
ffffffff88061883 ffff88002d8c1eb8 ffff88003fcf8000 ffff88002d8c1eb8
Jul 26 14:41:58 DS-1-29-SLES10-SP2-64bit-Xen kernel:
ffffffff8806245b ffff88002d8c1ec0 ffff88002d8c1ec0 ffff88002d8c1ed0
Jul 26 14:41:58 DS-1-29-SLES10-SP2-64bit-Xen kernel:
ffff88002d8c1ed0 ffff88002d8c1f10
Jul 26 14:41:58 DS-1-29-SLES10-SP2-64bit-Xen kernel: Call Trace:
<ffffffff88061883>{:scsi_mod:scsi_eh_flush_done_q+235}
Jul 26 14:41:58 DS-1-29-SLES10-SP2-64bit-Xen kernel:
<ffffffff8806245b>{:scsi_mod:scsi_error_handler+816}
Jul 26 14:41:58 DS-1-29-SLES10-SP2-64bit-Xen kernel:
<ffffffff8806212b>{:scsi_mod:scsi_error_handler+0}
<ffffffff80142c5d>{keventd_create_kthread+0}
Jul 26 14:41:58 DS-1-29-SLES10-SP2-64bit-Xen kernel:
<ffffffff80142f0d>{kthread+212}<ffffffff8010abdc>{child_rip+10}
Jul 26 14:41:58 DS-1-29-SLES10-SP2-64bit-Xen kernel:
<ffffffff80142c5d>{keventd_create_kthread+0}<ffffffff80142e39>{kthread
+0}
Jul 26 14:41:58 DS-1-29-SLES10-SP2-64bit-Xen kernel:
<ffffffff8010abd2>{child_rip+0}
Jul 26 14:41:58 DS-1-29-SLES10-SP2-64bit-Xen kernel:
Jul 26 14:41:58 DS-1-29-SLES10-SP2-64bit-Xen kernel: Code: Bad RIP
value.
Jul 26 14:41:58 DS-1-29-SLES10-SP2-64bit-Xen kernel: RIP
<0000000000000000>{_stext+2146431224} RSP<ffff88002d8c1e98>
Jul 26 14:41:58 DS-1-29-SLES10-SP2-64bit-Xen kernel: CR2:
0000000000000000
Jul 26 14:42:01 DS-1-29-SLES10-SP2-64bit-Xen agetty[12412]: /dev/xvc0:
No such file or directory
Jul 26 14:42:11 DS-1-29-SLES10-SP2-64bit-Xen agetty[12413]: /dev/xvc0:
No such file or directory
Jul 26 14:42:21 DS-1-29-SLES10-SP2-64bit-Xen agetty[12414]: /dev/xvc0:
No such file or directory
Jul 26 14:42:31 DS-1-29-SLES10-SP2-64bit-Xen agetty[12415]: /dev/xvc0:
No such file or directory
Jul 26 14:42:41 DS-1-29-SLES10-SP2-64bit-Xen agetty[12416]: /dev/xvc0:
No such file or directory
Jul 26 14:42:51 DS-1-29-SLES10-SP2-64bit-Xen agetty[12417]: /dev/xvc0:
No such file or directory
Jul 26 14:43:01 DS-1-29-SLES10-SP2-64bit-Xen init: Id "x0" respawning
too fast: disabled for 5 minutes
Jul 26 14:47:23 DS-1-29-SLES10-SP2-64bit-Xen syslog-ng[1480]: STATS:
dropped 0
Jul 26 14:48:02 DS-1-29-SLES10-SP2-64bit-Xen agetty[12450]: /dev/xvc0:
No such file or directory
Jul 26 14:48:12 DS-1-29-SLES10-SP2-64bit-Xen agetty[12451]: /dev/xvc0:
No such file or directory
Jul 26 14:48:22 DS-1-29-SLES10-SP2-64bit-Xen agetty[12452]: /dev/xvc0:
No such file or directory
On Jul 24, 2:19 am, Anil<pratapagiri...@gmail.com> wrote:
Found the reason for the iscsi connection error. Still trying to
analyze why its happening. We are using BIO_RW_SYNC flag in the bio->bi_rw.
This is causing the connection to be dropped. Dont know
why....yet.
--
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.
