From owner-freebsd-scsi@FreeBSD.ORG Mon Sep 8 02:22:27 2008 Return-Path: Delivered-To: freebsd-scsi@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8EFB01065693 for ; Mon, 8 Sep 2008 02:22:27 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 7C9888FC1F for ; Mon, 8 Sep 2008 02:22:27 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.2/8.14.2) with ESMTP id m882MR39006810 for ; Mon, 8 Sep 2008 02:22:27 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.2/8.14.1/Submit) id m882MQuH006806 for freebsd-scsi@FreeBSD.org; Mon, 8 Sep 2008 02:22:26 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 8 Sep 2008 02:22:26 GMT Message-Id: <200809080222.m882MQuH006806@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-scsi@FreeBSD.org Cc: Subject: Current problem reports assigned to freebsd-scsi@FreeBSD.org X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Sep 2008 02:22:27 -0000 The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o kern/126866 scsi [isp] [panic] kernel panic on card initialization o kern/124667 scsi [amd] [panic] FreeBSD-7 kernel page faults at amd-scsi o kern/123674 scsi [ahc] ahc driver dumping o kern/123666 scsi [aac] attach fails with Adaptec SAS RAID 3805 controll o sparc/121676 scsi [iscsi] iscontrol do not connect iscsi-target on sparc o kern/120487 scsi [sg] scsi_sg incompatible with scanners o kern/120247 scsi [mpt] FreeBSD 6.3 and LSI Logic 1030 = only 3.300MB/s o kern/119668 scsi [cam] [patch] certain errors are too verbose comparing o kern/114597 scsi [sym] System hangs at SCSI bus reset with dual HBAs o kern/110847 scsi [ahd] Tyan U320 onboard problem with more than 3 disks o kern/99954 scsi [ahc] reading from DVD failes on 6.x [regression] o kern/94838 scsi Kernel panic while mounting SD card with lock switch o o kern/92798 scsi [ahc] SCSI problem with timeouts o kern/90282 scsi [sym] SCSI bus resets cause loss of ch device o kern/76178 scsi [ahd] Problem with ahd and large SCSI Raid system o kern/74627 scsi [ahc] [hang] Adaptec 2940U2W Can't boot 5.3 s kern/61165 scsi [panic] kernel page fault after calling cam_send_ccb o kern/60641 scsi [sym] Sporadic SCSI bus resets with 53C810 under load o kern/60598 scsi wire down of scsi devices conflicts with config s kern/57398 scsi [mly] Current fails to install on mly(4) based RAID di o kern/52638 scsi [panic] SCSI U320 on SMP server won't run faster than o kern/44587 scsi dev/dpt/dpt.h is missing defines required for DPT_HAND o kern/40895 scsi wierd kernel / device driver bug o kern/39388 scsi ncr/sym drivers fail with 53c810 and more than 256MB m o kern/38828 scsi [dpt] [request] DPT PM2012B/90 doesn't work o kern/35234 scsi World access to /dev/pass? (for scanner) requires acce 26 problems total. Bugs can be in one of several states: o - open A problem report has been submitted, no sanity checking performed. a - analyzed The problem is understood and a solution is being sought. f - feedback Further work requires additional information from the originator or the community - possibly confirmation of the effectiveness of a proposed solution. p - patched A patch has been committed, but some issues (MFC and / or confirmation from originator) are still open. r - repocopy The resolution of the problem report is dependent on a repocopy operation within the CVS repository which is awaiting completion. s - suspended The problem is not being worked on, due to lack of information or resources. This is a prime candidate for somebody who is looking for a project to do. If the problem cannot be solved at all, it will be closed, rather than suspended. c - closed A problem report is closed when any changes have been integrated, documented, and tested -- or when fixing the problem is abandoned. From owner-freebsd-scsi@FreeBSD.ORG Tue Sep 9 21:28:18 2008 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 039D61065677 for ; Tue, 9 Sep 2008 21:28:18 +0000 (UTC) (envelope-from kolpanen@qads.kearfott.com) Received: from mailhost.kearfott.com (mailhost.kearfott.com [192.77.142.195]) by mx1.freebsd.org (Postfix) with ESMTP id A1B838FC12 for ; Tue, 9 Sep 2008 21:28:17 +0000 (UTC) (envelope-from kolpanen@qads.kearfott.com) Received: from qads.kearfott.com (qads.kearfott.com [172.18.1.1]) by mailhost.kearfott.com (8.13.1/8.13.1) with ESMTP id m89LFXGY030191 for ; Tue, 9 Sep 2008 17:15:33 -0400 Received: from qads.kearfott.com (localhost [127.0.0.1]) by qads.kearfott.com (8.13.1/8.13.1) with ESMTP id m89LFWVa014451 for ; Tue, 9 Sep 2008 17:15:32 -0400 (EDT) Received: (from kolpanen@localhost) by qads.kearfott.com (8.13.1/8.13.1/Submit) id m89LFW9S024655 for freebsd-scsi@freebsd.org; Tue, 9 Sep 2008 17:15:32 -0400 (EDT) Date: Tue, 9 Sep 2008 17:15:32 -0400 From: "Dennis R. Kolpanen" To: freebsd-scsi@freebsd.org Message-ID: <20080909211532.GA16009@qads.kearfott.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.1i Subject: iscsi initiator - system hang X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Sep 2008 21:28:18 -0000 On a FreeBSD 7.0 system, certain commands issued against any of the three mounted iscsi drives causes the system to "hang". In this context, hang means: the system continues to respond to pings sendmail stops accepting connections imapd stops accepting connections sshd stops accepting connections shell sessions already established stop accepting commands login at the system console is not possible The problem has been caused, so far, by dump, restore, and pax. These commands work perfectly if they are directed against one of the internal drives and not the iscsi drives. The failures noted above do not normally happen immediately after issuing one of these commands. The problems seem to build over a period of minutes or tens of minutes. Note that the dump/restore/pax commands can take hours to run. Nothing is written to the system console or any of the log files indicating a problem. The only way to recover from the hang is by means of the hardware reset button. When the system was first being set up and no other users were on it, shutting down all but one of the CPUs by means of sysctl and "machdep.hlt_cpus" allowed restoring about 150gb to the three iscsi drives. Once the machine was placed into production, massive hardware problems on an old server required this to be done immediately, this trick no longer works. An overview of the hardware involved: dual, quad-core Intel Xeon processors 16 gb RAM FreeBSD 7.0 amd64 release NetworkAppliance FAS2020 SAN generic kernel A complete dmesg output can be provided if desired. By default, iscontrol creates the iscsi drives with the number of tags set to one. The performance of the iscsi drives with this default setting was quite poor. Based on a recommendation made on a mailing list some time ago, /etc/iscsi.conf was changed to set the tags to 128. This had a dramatic improvement on the iscsi performance. Testing on the system that was rushed into production is not really possible. However, within the next week or so, a nearly identical system should become available and this one could be used for testing. Any ideas on what could be wrong? Any solutions? Thanks for your help. Dennis R. Kolpanen From owner-freebsd-scsi@FreeBSD.ORG Wed Sep 10 07:01:07 2008 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 85F00106566B for ; Wed, 10 Sep 2008 07:01:07 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from cs1.cs.huji.ac.il (cs1.cs.huji.ac.il [132.65.16.10]) by mx1.freebsd.org (Postfix) with ESMTP id 3BE108FC13 for ; Wed, 10 Sep 2008 07:01:07 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from pampa.cs.huji.ac.il ([132.65.80.32]) by cs1.cs.huji.ac.il with esmtp id 1KdJFB-000GTJ-98; Wed, 10 Sep 2008 09:32:01 +0300 X-Mailer: exmh version 2.7.2 01/07/2005 with nmh-1.2 To: "Dennis R. Kolpanen" In-reply-to: <20080909211532.GA16009@qads.kearfott.com> References: <20080909211532.GA16009@qads.kearfott.com> Comments: In-reply-to "Dennis R. Kolpanen" message dated "Tue, 09 Sep 2008 17:15:32 -0400." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 10 Sep 2008 09:32:01 +0300 From: Danny Braniss Message-ID: Cc: freebsd-scsi@freebsd.org Subject: Re: iscsi initiator - system hang X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Sep 2008 07:01:07 -0000 > On a FreeBSD 7.0 system, certain commands issued against any of the > three mounted iscsi drives causes the system to "hang". In this > context, hang means: > > the system continues to respond to pings > sendmail stops accepting connections > imapd stops accepting connections > sshd stops accepting connections > shell sessions already established stop accepting commands > login at the system console is not possible > > The problem has been caused, so far, by dump, restore, and pax. These > commands work perfectly if they are directed against one of the > internal drives and not the iscsi drives. The failures noted above do > not normally happen immediately after issuing one of these commands. > The problems seem to build over a period of minutes or tens of > minutes. Note that the dump/restore/pax commands can take hours to > run. > > Nothing is written to the system console or any of the log files > indicating a problem. The only way to recover from the hang is by > means of the hardware reset button. > > When the system was first being set up and no other users were on it, > shutting down all but one of the CPUs by means of sysctl and > "machdep.hlt_cpus" allowed restoring about 150gb to the three iscsi > drives. Once the machine was placed into production, massive hardware > problems on an old server required this to be done immediately, this > trick no longer works. > > An overview of the hardware involved: > > dual, quad-core Intel Xeon processors > 16 gb RAM FreeBSD 7.0 amd64 release > NetworkAppliance FAS2020 SAN > generic kernel > > A complete dmesg output can be provided if desired. > > By default, iscontrol creates the iscsi drives with the number of tags > set to one. The performance of the iscsi drives with this default > setting was quite poor. Based on a recommendation made on a mailing > list some time ago, /etc/iscsi.conf was changed to set the tags to > 128. This had a dramatic improvement on the iscsi performance. > > Testing on the system that was rushed into production is not really > possible. However, within the next week or so, a nearly identical > system should become available and this one could be used for testing. > > Any ideas on what could be wrong? Any solutions? > maybe, but first, can you send me the output of 'sysctl net.iscsi'? danny > Thanks for your help. > > Dennis R. Kolpanen > _______________________________________________ > freebsd-scsi@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-scsi > To unsubscribe, send any mail to "freebsd-scsi-unsubscribe@freebsd.org" > From owner-freebsd-scsi@FreeBSD.ORG Wed Sep 10 11:52:28 2008 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 64B531065679 for ; Wed, 10 Sep 2008 11:52:28 +0000 (UTC) (envelope-from kolpanen@qads.kearfott.com) Received: from mailhost.kearfott.com (mailhost.kearfott.com [192.77.142.195]) by mx1.freebsd.org (Postfix) with ESMTP id 308928FC14 for ; Wed, 10 Sep 2008 11:52:28 +0000 (UTC) (envelope-from kolpanen@qads.kearfott.com) Received: from qads.kearfott.com (qads.kearfott.com [172.18.1.1]) by mailhost.kearfott.com (8.13.1/8.13.1) with ESMTP id m8ABq02I010285; Wed, 10 Sep 2008 07:52:00 -0400 Received: from qads.kearfott.com (localhost [127.0.0.1]) by qads.kearfott.com (8.13.1/8.13.1) with ESMTP id m8ABq0P0000598; Wed, 10 Sep 2008 07:52:00 -0400 (EDT) Received: (from kolpanen@localhost) by qads.kearfott.com (8.13.1/8.13.1/Submit) id m8ABq0kL018683; Wed, 10 Sep 2008 07:52:00 -0400 (EDT) Date: Wed, 10 Sep 2008 07:51:59 -0400 From: "Dennis R. Kolpanen" To: Danny Braniss Message-ID: <20080910115159.GA28900@qads.kearfott.com> References: <20080909211532.GA16009@qads.kearfott.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i Cc: freebsd-scsi@freebsd.org Subject: Re: iscsi initiator - system hang X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Sep 2008 11:52:28 -0000 On Wed, Sep 10, 2008 at 09:32:01AM +0300, Danny Braniss wrote: > > On a FreeBSD 7.0 system, certain commands issued against any of the > > three mounted iscsi drives causes the system to "hang". In this > > context, hang means: > > > > the system continues to respond to pings > > sendmail stops accepting connections > > imapd stops accepting connections > > sshd stops accepting connections > > shell sessions already established stop accepting commands > > login at the system console is not possible > > > > The problem has been caused, so far, by dump, restore, and pax. These > > commands work perfectly if they are directed against one of the > > internal drives and not the iscsi drives. The failures noted above do > > not normally happen immediately after issuing one of these commands. > > The problems seem to build over a period of minutes or tens of > > minutes. Note that the dump/restore/pax commands can take hours to > > run. > > > > Nothing is written to the system console or any of the log files > > indicating a problem. The only way to recover from the hang is by > > means of the hardware reset button. > > > > When the system was first being set up and no other users were on it, > > shutting down all but one of the CPUs by means of sysctl and > > "machdep.hlt_cpus" allowed restoring about 150gb to the three iscsi > > drives. Once the machine was placed into production, massive hardware > > problems on an old server required this to be done immediately, this > > trick no longer works. > > > > An overview of the hardware involved: > > > > dual, quad-core Intel Xeon processors > > 16 gb RAM FreeBSD 7.0 amd64 release > > NetworkAppliance FAS2020 SAN > > generic kernel > > > > A complete dmesg output can be provided if desired. > > > > By default, iscontrol creates the iscsi drives with the number of tags > > set to one. The performance of the iscsi drives with this default > > setting was quite poor. Based on a recommendation made on a mailing > > list some time ago, /etc/iscsi.conf was changed to set the tags to > > 128. This had a dramatic improvement on the iscsi performance. > > > > Testing on the system that was rushed into production is not really > > possible. However, within the next week or so, a nearly identical > > system should become available and this one could be used for testing. > > > > Any ideas on what could be wrong? Any solutions? > > > > maybe, but first, can you send me the output of 'sysctl net.iscsi'? > > danny > Danny, No problem. Here it is: net.iscsi.driver_version: 2.0.99 net.iscsi.isid: DIB00 net.iscsi.sessions: 1 net.iscsi.0.targetname: iqn.1992-08.com.netapp:sn.135029528 net.iscsi.0.targeaddress: 10.172.172.1 net.iscsi.0.stats: recv=1288005 sent=1287999 flags=0x0000011b pdus-alloc=0 pdus-max=220 cws=64 cmd=afa32 exp=afa32 max=afa71 stat=afa32 itt=afa32 net.iscsi.0.pid: 916 Thanks. Dennis