From owner-freebsd-scsi@FreeBSD.ORG Tue Apr 11 03:15:06 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 06FCF16A400 for ; Tue, 11 Apr 2006 03:15:05 +0000 (UTC) (envelope-from tom@uniserve.com) Received: from mx4.uniserve.ca (mx4.uniserve.ca [216.113.192.45]) by mx1.FreeBSD.org (Postfix) with ESMTP id B25CC43D45 for ; Tue, 11 Apr 2006 03:15:05 +0000 (GMT) (envelope-from tom@uniserve.com) Received: from mgmt.uniserve.ca ([216.113.192.30]) by mx4.uniserve.ca with esmtp (Exim 4.50) id 1FT9LN-000Gpe-Cp; Mon, 10 Apr 2006 20:15:05 -0700 Date: Mon, 10 Apr 2006 20:15:05 -0700 (PDT) From: Tom Samplonius X-X-Sender: tom@mgmt.uniserve.ca To: Eric Anderson In-Reply-To: <443B1D8E.5000805@centtech.com> Message-ID: <20060410201012.X46924@mgmt.uniserve.ca> References: <443AA86A.5020207@centtech.com> <20060410120647.W46924@mgmt.uniserve.ca> <443AC4E4.9030808@centtech.com> <20060410143733.V89316@mgmt.uniserve.ca> <443B1D8E.5000805@centtech.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Scanner: OK. Scanned. 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:15:06 -0000 >>>> 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? You will probably have to reboot, actually. The isp driver will probably get confused if the port changed type. So do a shutdown, change the port, and then boot up. >>> 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? I don't know how do this on QLogic switch. If it is actually a switch, it should have a cli or http management interface to configure ports. If it does not have an interface, it may be a hub, in which it is actually a loop (fibre channel hubs are effectively a daisy chained loop of ports). > Thanks for your help! > > > Eric Tom