From owner-freebsd-scsi@FreeBSD.ORG Thu Jul 14 10:48:17 2005 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 D8FEE16A41C for ; Thu, 14 Jul 2005 10:48:17 +0000 (GMT) (envelope-from rainer@ultra-secure.de) Received: from bsd.ultra-secure.de (bsd.ultra-secure.de [62.146.20.26]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2374643D53 for ; Thu, 14 Jul 2005 10:48:16 +0000 (GMT) (envelope-from rainer@ultra-secure.de) Received: (qmail 70149 invoked by uid 1005); 14 Jul 2005 10:48:16 -0000 Received: from rainer@ultra-secure.de by bsd.ultra-secure.de by uid 89 with qmail-scanner-1.22 (clamdscan: 0.85. spamassassin: 2.64. Clear:RC:1(213.196.191.65):. Processed in 0.029718 secs); 14 Jul 2005 10:48:16 -0000 Received: from unknown (HELO ?192.168.100.179?) (rainer@ultra-secure.de@213.196.191.65) by bsd.ultra-secure.de with (DHE-RSA-AES256-SHA encrypted) SMTP; 14 Jul 2005 10:48:15 -0000 Message-ID: <42D642EB.1090405@ultra-secure.de> Date: Thu, 14 Jul 2005 12:48:11 +0200 From: Rainer Duffner User-Agent: Mozilla Thunderbird 1.0.5 (X11/20050711) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Scott Long References: <42D404CC.4010703@ultra-secure.de> <42D57D26.3010705@samsco.org> In-Reply-To: <42D57D26.3010705@samsco.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-scsi@freebsd.org Subject: Re: FreeBSD 5.4-i386, isp(4) and an EVA3000 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: Thu, 14 Jul 2005 10:48:18 -0000 Scott Long wrote: > Rainer Duffner wrote: > >> Hi, >> >> I've just installed FreeBSD 5.4 on a HP blade, connected to our EVA >> 3000 SAN. >> >> The sysinstall-kernel doesn't have the ispfw-module and it didn't >> recognize the LUNs - is there a way to load that module from the >> original install-medium or do I have to bake my own? >> OK, so this is the test-blade that has a hard-disk inside and I >> installed on that, built my own kernel that had ispfw(4), booted and >> ... couldn't get to FreeBSD, because it had now found the SAN and >> moved the "old" da0 to da8 or so... >> >> Didum...Re-install, this time I see a lot of LUNs from the SAN, and >> install on da0, all went well, I can boot that - beautiful, compared >> to the likes of RHEL... > > > > Read the section in /sys/conf/NOTES that talks about wiring down > SCSI IDs and LUNs to particular device numbers. > > Scott OK, I knew that (sort of). But I'm still curious why I am seeing so many ghost-LUNS. Another thing: when I tried to enlarge such a VDISK, it didn't work quite the way I originally thought (which you can blame on my thinking) - it created a 2nd partition on the same LUN with the rest of the space. So I should rather create a new LUN and use vinum to concatenate them together, right? Does that work "online"? But what was more annoying was the fact that when I ran camcontrol rescan, the whole machine just froze. (I had unmounted the slice, AFAICR) Is this normal? cheers, Rainer