From owner-freebsd-scsi@FreeBSD.ORG Tue Apr 11 03:08:13 2006 Return-Path: X-Original-To: freebsd-scsi@freebsd.org Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 599DE16A404 for ; Tue, 11 Apr 2006 03:08:13 +0000 (UTC) (envelope-from anderson@centtech.com) Received: from mh2.centtech.com (moat3.centtech.com [207.200.51.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id C185B43D46 for ; Tue, 11 Apr 2006 03:08:12 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from [192.168.42.21] (andersonbox1.centtech.com [192.168.42.21]) by mh2.centtech.com (8.13.1/8.13.1) with ESMTP id k3B38BZG054291; Mon, 10 Apr 2006 22:08:11 -0500 (CDT) (envelope-from anderson@centtech.com) Message-ID: <443B1D8E.5000805@centtech.com> Date: Mon, 10 Apr 2006 22:07:58 -0500 From: Eric Anderson User-Agent: Thunderbird 1.5 (X11/20060402) MIME-Version: 1.0 To: Tom Samplonius References: <443AA86A.5020207@centtech.com> <20060410120647.W46924@mgmt.uniserve.ca> <443AC4E4.9030808@centtech.com> <20060410143733.V89316@mgmt.uniserve.ca> In-Reply-To: <20060410143733.V89316@mgmt.uniserve.ca> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.87.1/1389/Mon Apr 10 07:58:55 2006 on mh2.centtech.com X-Virus-Status: Clean Cc: freebsd-scsi@freebsd.org Subject: Re: LIP destroyed xxx active commands 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, 11 Apr 2006 03:08:13 -0000 Tom Samplonius wrote: > > On Mon, 10 Apr 2006, Eric Anderson wrote: > >> Tom Samplonius wrote: >>> >>> Eric, >>> >>> It seems that isp0 is connected to a loop topology network (as >>> opposed to a point to point, or fabric), and something keeps >>> initializing the loop by sending a LIP command. >>> >>> Are you plugging or unplugging things into the loop all of the >>> time? Or are you loop part on a switch, and someone else is plugging >>> or unplugging things from the fabric? If you are going straight into >>> a switch, it might be better to change the port to a fabric port >>> instead. >> >> >> This host has it's isp device directly connected to a fiber channel >> array. > > Probably should use point-to-point mode instead. See if you can > change the port type on the array controller. Ok - I can do that. If I do that, will that disrupt filesystem activity? >> The array is not disappearing, or being rebooted, nor is there any >> other machine rebooting or resetting. I see these same errors on >> another box that has 3 arrays connected to a qlogic switch. I seem to >> only see these when the machine is heavily accessing the disks. > > Same here. You shouldn't see LIPs on a fabric. So the QLogic switch > must be trying to maintain a loop per port. > > I suspect that loop mode is also less stable than point-to-point or > fabric. There is an indication in the isp manpage that it is possible > for the driver to hang on boot waiting for a LIP. The solution to that > problem has been to force a LIP (unplug something), or don't use a loop > mode. What do I need to change on the qlogic switch/initiator/target ends to force things? Thanks for your help! Eric -- ------------------------------------------------------------------------ Eric Anderson Sr. Systems Administrator Centaur Technology Anything that works is better than anything that doesn't. ------------------------------------------------------------------------