From owner-freebsd-scsi@FreeBSD.ORG Sun May 23 02:06:09 2004 Return-Path: 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 EED8C16A4CE; Sun, 23 May 2004 02:06:08 -0700 (PDT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9D42543D45; Sun, 23 May 2004 02:06:08 -0700 (PDT) (envelope-from scottl@freebsd.org) Received: from freebsd.org (junior-wifi.samsco.home [192.168.0.11]) (authenticated bits=0) by pooker.samsco.org (8.12.11/8.12.10) with ESMTP id i4MFT10s050190; Sat, 22 May 2004 09:29:01 -0600 (MDT) (envelope-from scottl@freebsd.org) Message-ID: <40AF7052.9000609@freebsd.org> Date: Sat, 22 May 2004 09:22:58 -0600 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.6) Gecko/20040304 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "J.D. Bronson" References: <6.1.1.1.2.20040522092527.00be43e8@cheyenne.wixb.com> In-Reply-To: <6.1.1.1.2.20040522092527.00be43e8@cheyenne.wixb.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, hits=0.0 required=3.8 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on pooker.samsco.org cc: freebsd-scsi@freebsd.org cc: freebsd-performance@freebsd.org cc: freebsd-questions@freebsd.org cc: mjacob@freebsd.org Subject: Re: LSI 20320R Raid Card X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 May 2004 09:06:09 -0000 J.D. Bronson wrote: > I have asked this and no one replied, but I have more information... > > The card seems very well supported (mpt) but yet when I setup a RAID > MIRROR and it is resyncing - the card DOES tell Freebsd 5.2.1, but the > message is unrecognized: > > ============================================ > Waiting 10 seconds for SCSI devices to settle > mpt0: Unknown event 0xb > mpt0: Unknown event 0xb > > GEOM: create disk da0 dp=0xc7b72050 > ============================================= > > Is there plans to fix this so that the card and the driver can tell the OS > whats going on? > > Thanks. > > > The mpt and amr drivers are largely unmaintained right now as LSI no longer sponsors an engineer to take care of them. I'm not sure what else to say about that other than we would gladly accept a new maintainer. Scott From owner-freebsd-scsi@FreeBSD.ORG Fri May 28 07:03:46 2004 Return-Path: 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 762BC16A4CE for ; Fri, 28 May 2004 07:03:46 -0700 (PDT) Received: from mail.sandvine.com (sandvine.com [199.243.201.138]) by mx1.FreeBSD.org (Postfix) with ESMTP id E3DFA43D46 for ; Fri, 28 May 2004 07:03:33 -0700 (PDT) (envelope-from ahoff@sandvine.com) Received: by mail.sandvine.com with Internet Mail Service (5.5.2657.72) id ; Fri, 28 May 2004 10:03:03 -0400 Message-ID: From: Alex Hoff To: "'freebsd-scsi@freebsd.org'" Date: Fri, 28 May 2004 10:03:03 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2657.72) Content-Type: text/plain; charset="iso-8859-1" Subject: FreeBSD and extremely large volumes X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 May 2004 14:03:46 -0000 Hi, We have a FreeBSD 4.7 system with an Adaptec 2200S RAID controller and 14 x 140 gig IBM drives. We have run in to an issue that when all drives are combined into a single volume, the OS can't handle the large number of sectors. Since the RAID controller sets the sector size to 512, and we can not change that, the total number of sectors in our system is between 2^31 and 2^32. Well utilities such as fdisk use a signed integer and here in lies the problem, the total number of sectors is now negative. Oops. To make things worse, as soon as 300 gig drives become available, we will have 14 x 300 which will result in the number of sectors > 2^32, thus overflowing the int. I am sure that someone else has a setup with such a large amount of storage. What have these people done to overcome this limitation? Since we can't change the sector size, what other tricks can we use? Keeping the drive as a single volume is required for the intended application. Any help would be greatly appreciated, Alex Hoff ahoff@sandvine.com