Re: Crash tgtd and tgtadm with more than 112 volumes.
FUJITA Tomonori schrieb: Let me know if I can provide any additional info. >>> You are on the wrong mailing list. This is for the Open-iSCSI _initiator_. >>> The mailing >>> list you want is for the Open-iSCSI _target_, which is: >>> iscsitarget-de...@lists.sourceforge.net. >> The address is s...@vger.kernel.org for a year or so, the >> iscsitarget-de...@lists.sourceforge.net is an old address which is not >> used any more. > > This part is not correct. > > iscsitarget-de...@lists.sourceforge.net is the mailing list for iSCSI > Enterprise Target project (IET), which is not tgt project. I had > maintained IET but we have never used IET mailing list for tgt. > > FYI, our old mailing list is stgt-de...@lists.berlios.de. Of course, my mistake. -- Tomasz Chmielewski http://wpkg.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 -~--~~~~--~~--~--~---
Re: Crash tgtd and tgtadm with more than 112 volumes.
On Tue, 10 Mar 2009 23:23:30 +0100 Tomasz Chmielewski wrote: > Konrad Rzeszutek schrieb: > > On Tue, Mar 10, 2009 at 02:52:41PM -0700, Ben Greear wrote: > >> I wrote a script to create lots of iscsi volumes on loop devices. > >> > >> Seems to run fine up to 111, and then tgtd crashes and tgtadm > >> gets a buffer overflow. > >> > >> The script I used to create the problem and a capture of the > >> crash is attached. > >> > >> I'm using standard RPMs on Fedora 10, kernel > >> Linux iSCSi-test 2.6.27.15-170.2.24.fc10.x86_64 #1 SMP Wed Feb 11 23:14:31 > >> EST 2009 x86_64 x86_64 x86_64 GNU/Linux > >> > >> Let me know if I can provide any additional info. > > > > You are on the wrong mailing list. This is for the Open-iSCSI _initiator_. > > The mailing > > list you want is for the Open-iSCSI _target_, which is: > > iscsitarget-de...@lists.sourceforge.net. > > The address is s...@vger.kernel.org for a year or so, the > iscsitarget-de...@lists.sourceforge.net is an old address which is not > used any more. This part is not correct. iscsitarget-de...@lists.sourceforge.net is the mailing list for iSCSI Enterprise Target project (IET), which is not tgt project. I had maintained IET but we have never used IET mailing list for tgt. FYI, our old mailing list is stgt-de...@lists.berlios.de. > CC: s...@vger.kernel.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 -~--~~~~--~~--~--~---
Re: Crash tgtd and tgtadm with more than 112 volumes.
Tomasz Chmielewski wrote: >>> Let me know if I can provide any additional info. >> You are on the wrong mailing list. This is for the Open-iSCSI _initiator_. >> The mailing >> list you want is for the Open-iSCSI _target_, which is: >> iscsitarget-de...@lists.sourceforge.net. > > The address is s...@vger.kernel.org for a year or so, the > iscsitarget-de...@lists.sourceforge.net is an old address which is not > used any more. > > CC: s...@vger.kernel.org Thanks, I tried to forward it off to stgt, hopefully it will make it. Ben -- Ben Greear Candela Technologies Inc http://www.candelatech.com --~--~-~--~~~---~--~~ 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: Crash tgtd and tgtadm with more than 112 volumes.
Konrad Rzeszutek schrieb: > On Tue, Mar 10, 2009 at 02:52:41PM -0700, Ben Greear wrote: >> I wrote a script to create lots of iscsi volumes on loop devices. >> >> Seems to run fine up to 111, and then tgtd crashes and tgtadm >> gets a buffer overflow. >> >> The script I used to create the problem and a capture of the >> crash is attached. >> >> I'm using standard RPMs on Fedora 10, kernel >> Linux iSCSi-test 2.6.27.15-170.2.24.fc10.x86_64 #1 SMP Wed Feb 11 23:14:31 >> EST 2009 x86_64 x86_64 x86_64 GNU/Linux >> >> Let me know if I can provide any additional info. > > You are on the wrong mailing list. This is for the Open-iSCSI _initiator_. > The mailing > list you want is for the Open-iSCSI _target_, which is: > iscsitarget-de...@lists.sourceforge.net. The address is s...@vger.kernel.org for a year or so, the iscsitarget-de...@lists.sourceforge.net is an old address which is not used any more. CC: s...@vger.kernel.org -- Tomasz Chmielewski http://wpkg.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 -~--~~~~--~~--~--~---
Re: Crash tgtd and tgtadm with more than 112 volumes.
On Tue, Mar 10, 2009 at 02:52:41PM -0700, Ben Greear wrote: > I wrote a script to create lots of iscsi volumes on loop devices. > > Seems to run fine up to 111, and then tgtd crashes and tgtadm > gets a buffer overflow. > > The script I used to create the problem and a capture of the > crash is attached. > > I'm using standard RPMs on Fedora 10, kernel > Linux iSCSi-test 2.6.27.15-170.2.24.fc10.x86_64 #1 SMP Wed Feb 11 23:14:31 > EST 2009 x86_64 x86_64 x86_64 GNU/Linux > > Let me know if I can provide any additional info. You are on the wrong mailing list. This is for the Open-iSCSI _initiator_. The mailing list you want is for the Open-iSCSI _target_, which is: iscsitarget-de...@lists.sourceforge.net. --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Crash tgtd and tgtadm with more than 112 volumes.
I wrote a script to create lots of iscsi volumes on loop devices. Seems to run fine up to 111, and then tgtd crashes and tgtadm gets a buffer overflow. The script I used to create the problem and a capture of the crash is attached. I'm using standard RPMs on Fedora 10, kernel Linux iSCSi-test 2.6.27.15-170.2.24.fc10.x86_64 #1 SMP Wed Feb 11 23:14:31 EST 2009 x86_64 x86_64 x86_64 GNU/Linux Let me know if I can provide any additional info. Thanks, Ben -- Ben Greear Candela Technologies Inc http://www.candelatech.com --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~--- # Found this in /var/log/messages tgtd[2665]: segfault at 90 ip 003185c0c231 sp 7fff7528fab0 error 4 in libpthread-2.9.so[3185c0+17000] # This is output from my script as it's createing things. ... Running -:tgtadm --lld iscsi --op new --mode logicalunit --tid 111 --lun 1 -b /dev/loop111:- Running -:tgtadm --lld iscsi --op bind --mode target --tid 111 -I ALL:- Running -:cp /export/iscsi/disk.100m.ext3 /export/iscsi/disk112:- Running -:losetup /dev/loop112 /export/iscsi/disk112:- Running -:tgtadm --lld iscsi --op new --mode target --tid=112 --targetname iqn.2009-02.com.lanforge:for.all.112:- Running -:tgtadm --lld iscsi --op new --mode logicalunit --tid 112 --lun 1 -b /dev/loop112:- *** buffer overflow detected ***: tgtadm terminated === Backtrace: = /lib64/libc.so.6(__fortify_fail+0x37)[0x31850ff4c7] /lib64/libc.so.6[0x31850fd370] /lib64/libc.so.6(__read_chk+0x28)[0x31850fd8a8] tgtadm[0x4010be] tgtadm[0x401f17] /lib64/libc.so.6(__libc_start_main+0xe6)[0x318501e576] tgtadm[0x400c59] === Memory map: 0040-00404000 r-xp fd:00 834180 /usr/sbin/tgtadm 00603000-00605000 rw-p 3000 fd:00 834180 /usr/sbin/tgtadm 00b05000-00b28000 rw-p 00b05000 00:00 0 [heap] 3183c0-3183c2 r-xp fd:00 3760356 /lib64/ld-2.9.so 3183e1f000-3183e2 r--p 0001f000 fd:00 3760356 /lib64/ld-2.9.so 3183e2-3183e21000 rw-p 0002 fd:00 3760356 /lib64/ld-2.9.so 318500-3185168000 r-xp fd:00 3760461 /lib64/libc-2.9.so 3185168000-3185368000 ---p 00168000 fd:00 3760461 /lib64/libc-2.9.so 3185368000-318536c000 r--p 00168000 fd:00 3760461 /lib64/libc-2.9.so 318536c000-318536d000 rw-p 0016c000 fd:00 3760461 /lib64/libc-2.9.so 318536d000-3185372000 rw-p 318536d000 00:00 0 3192a0-3192a16000 r-xp fd:00 3760493 /lib64/libgcc_s-4.3.2-20081105.so.1 3192a16000-3192c16000 ---p 00016000 fd:00 3760493 /lib64/libgcc_s-4.3.2-20081105.so.1 3192c16000-3192c17000 rw-p 00016000 fd:00 3760493 /lib64/libgcc_s-4.3.2-20081105.so.1 7f1af8b1-7f1af8b12000 rw-p 7f1af8b1 00:00 0 7f1af8b28000-7f1af8b2a000 rw-p 7f1af8b28000 00:00 0 7fff00b14000-7fff00b29000 rw-p 7ffea000 00:00 0 [stack] 7fff00bfe000-7fff00bff000 r-xp 7fff00bfe000 00:00 0 [vdso] ff60-ff601000 r-xp 00:00 0 [vsyscall] Running -:tgtadm --lld iscsi --op bind --mode target --tid 112 -I ALL:- tgtadm: can't connect to the tgt daemon, Connection refused tgtadm: can't send the request to the tgt daemon, Transport endpoint is not connected Running -:cp /export/iscsi/disk.100m.ext3 /export/iscsi/disk113:- Running -:losetup /dev/loop113 /export/iscsi/disk113:- Running -:tgtadm --lld iscsi --op new --mode target --tid=113 --targetname iqn.2009-02.com.lanforge:for.all.113:- tgtadm: can't connect to the tgt daemon, Connection refused tgtadm: can't send the request to the tgt daemon, Transport endpoint is not connected Running -:tgtadm --lld iscsi --op new --mode logicalunit --tid 113 --lun 1 -b /dev/loop113:- tgtadm: can't connect to the tgt daemon, Connection refused tgtadm: can't send the request to the tgt daemon, Transport endpoint is not connected Running -:tgtadm --lld iscsi --op bind --mode target --tid 113 -I ALL:- tgtadm: can't connect to the tgt daemon, Connection refused tgtadm: can't send the request to the tgt daemon, Transport endpoint is not connected create_iscsi_targets.pl Description: Perl program
