u can always send to iet list that more people can help you.
feel curious, why u need initialr2t=yes?
ini rc6-363 is a very old version. if i am correct, it is open-iscsi
r363. now they have 488 i guess.
also u use dm-crypt.
assume u can reproduce this every time with dm-crypt now. could u try
this and see if can reproduce.
*) try latest iet;
*) try newer open-iscsi.
*) try no crypt volume here?
iet does not have many debug information, maybe u can turn on open-iscsi
debug and see where it hangs.
thanks a lot!
ming
-------- Forwarded Message --------
From: Thomas Scholz <tscholz@xxxxxxxxx>
To: mingz@xxxxxxxxxxx
Subject: Re: [Iscsitarget-devel] iscsitarget froze my system
Date: Mon, 13 Feb 2006 11:48:33 +0100
Hi,
ok here are more informations:
ietd.conf
Target iqn.2005-08.com.xinix:storage.disk1.sol
IncomingUser tscholz XXXXXXXXXXXXX
Lun 0 Path=/dev/mapper/sol,Type=fileio
Alias sol
MaxConnections 3
InitialR2T Yes
Target iqn.2005-08.com.xinix:storage.disk2.vol1
IncomingUser tscholz XXXXXXXXXXXXX
Lun 1 Path=/dev/mapper/vol1,Type=fileio
Alias vol1
MaxConnections 3
InitialR2T Yes
Target iqn.2005-08.com.xinix:storage.disk3.vol0
IncomingUser tscholz XXXXXXXXXXXXX
Lun 2 Path=/dev/mapper/vol0,Type=fileio
Alias vol0
MaxConnections 3
InitialR2T Yes
----------------
My setup for lun0 - lun2:
echo 0 $(blockdev --getsize /dev/hdc2) crypt twofish $pass 0 /dev/hdc2 0 |
dmsetup create sol
echo 0 $(blockdev --getsize /dev/hdc1) crypt twofish $pass 0 /dev/hdc1 0 |
dmsetup create vol0
echo 0 $(blockdev --getsize /dev/hdb1) crypt twofish $pass 0 /dev/hdb1 0 |
dmsetup create vol1
On the clientside run debian linux with kernel 2.6.12.4 (see attachment).
I use linux-iscsi-5.0.0.0.3rc6-363 to import my devices and import all with a
small initrd:
linuxrc:
PATH="/bin:/sbin"
portal="172.20.169.65"
path="/bin"
rootnode="0342fc"
echo "Network SCSI Adapter"
echo " mount /proc /sys .."
mount /proc
mount /sys
echo " start loopback device .."
ifconfig lo 127.0.0.1
echo " load modules .."
insmod /modules/scsi_transport_iscsi.ko
insmod /modules/iscsi_tcp.ko
# Daemon
echo " start daemon .."
$path/iscsid
# Login
echo " attach storage .."
$path/iscsiadm -m discovery --type sendtargets --portal $portal":3260"
$path/iscsiadm -m node --record $rootnode --login
for rec in $($path/iscsiadm -m discovery --type sendtargets --portal
$portal":3260"
| sed "s/^\[//g;s/\].*$//g" | grep -v $rootnode)
do
$path/iscsiadm -m node --record $rec --login
done
echo " set rootdevice 0x800 .."
echo 0x800 > /proc/sys/kernel/real-root-dev
echo "finish initrd support"
---------------------
I use the following iscsid.conf
node.active_cnx = 1
node.startup = manual
node.session.auth.username = tscholz
node.session.auth.password = XXXXXXXXXXXXX
node.session.timeo.replacement_timeout = 0
node.session.err_timeo.abort_timeout = 10
node.session.err_timeo.reset_timeout = 30
node.session.iscsi.InitialR2T = No
node.session.iscsi.ImmediateData = Yes
node.session.iscsi.FirstBurstLength = 262144
node.session.iscsi.MaxBurstLength = 16776192
node.session.iscsi.DefaultTime2Wait = 0
node.session.iscsi.DefaultTime2Retain = 0
node.session.iscsi.MaxConnections = 0
node.cnx[0].iscsi.HeaderDigest = None
node.cnx[0].iscsi.DataDigest = None
node.cnx[0].iscsi.MaxRecvDataSegmentLength = 65536
discovery.sendtargets.auth.authmethod = CHAP
discovery.sendtargets.auth.username = tscholz
discovery.sendtargets.auth.password = XXXXXXXXXXXXX
--------------
My current fstab looks like this:
# /etc/fstab: static file system information.
#
# <file system> <mount point> <type> <options> <dump> <pass>
/dev/sda / ext3 errors=remount-ro 0 1
/dev/sdc /vol1 ext3 errors=remount-ro 0 1
proc /proc proc defaults 0 0
sysfs /sys sysfs defaults 0 0
/dev/fd0 /floppy auto user,noauto 0 0
/dev/cdrom /cdrom iso9660 ro,user,noauto 0 0
none /vol tmpfs defaults 0 0
Client and server connected directly over ethernet with 100 Mbit.
After boot, I try some things like dd if=/dev/zero of=/tmp/zero_test bs=1M
count=2000 && dd if=/tmp/zero_test of=/dev/null or a rsync over files which
contains more then 1.7GB. rsync reads data from iscsi and write it to a
local disk in my client. If I run this programs after a while my iscsiserver
hang.
Is it possible to turn on detailed debugingissues in iscsi-target?
Regards
Thomas
On Monday 13 February 2006 03:23, Ming Zhang wrote:
> Hi
>
> we need more information on what kind of load u run from iscsi client
> side, if you can reproduce it, will be great. and what is you iscsi ini,
> from linux or windows... the more information, the easier for us to
> reproduce the bug, which is critical for debug.
>
> also what kind of device u export, especially if it is scsi device.
> 2.6.15 has a memory leak in scsi sub. not sure if they fixed in 2.6.15.3
> yet.
>
> thanks!
>
> mingz
>
> On Fri, 2006-02-10 at 11:37 +0100, Thomas Scholz wrote:
> > Hi,
> >
> > I am using iscsitarget 0.4.11 with kernel 2.6.15.3. Everything works
> > fine but after high load of data from my iscsiclient to iscsitarget my
> > server giving up.
> > My systemconsole is frozen. After reboot a can't find any log entry for
> > iscsitarget.
> > No problem has it with previous kernel 2.6.12 and iscsitarget 0.4.11.
> >
> >
> > Regards
> >
> > Thomas Scholz
> >
> > My config for 2.6.15.3 is attached.
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
|
