From owner-freebsd-stable@FreeBSD.ORG Wed Jan 23 15:29:30 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B617216A41B for ; Wed, 23 Jan 2008 15:29:30 +0000 (UTC) (envelope-from freebsd.stable1@gmail.com) Received: from rv-out-0910.google.com (rv-out-0910.google.com [209.85.198.185]) by mx1.freebsd.org (Postfix) with ESMTP id 7EBBF13C4CE for ; Wed, 23 Jan 2008 15:29:29 +0000 (UTC) (envelope-from freebsd.stable1@gmail.com) Received: by rv-out-0910.google.com with SMTP id l15so2754526rvb.43 for ; Wed, 23 Jan 2008 07:29:29 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; bh=cEUm7ImNM78LotHC1m9DkU4247bRMpFwrpzdaOvCQOs=; b=iJjzkd6LL8pWr1R9i+9hwlg8jwZNYq8hz9wQtzNQjht5LMMuA+PWB5JE+9Nm3BgCcYFsquxnq0K8TYnTWYqEl/xT8CBj5r953pt96dILwe7jS5Unwi9nML1CjCQJwBzczNOZEvOBgue6KQRG7CrxnsApBBEJ7J/wPirfAt3L/LM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=YeC9rPzL1i1FXPGXbaJpSLlv7Ghg6TjUN+SZvrmFBJpamWBNs/4nqodSA3MPgRltKAKqDi3jHJAVxWwPnl26R4Co3EiDmuPYX4Csq8zP9W3kUsl+JwGkNK8OOhyjqQf2EulpnamEL3NNEEZZvvxNAzli1awWuHOoeugkz2Ga7tY= Received: by 10.140.187.10 with SMTP id k10mr6423533rvf.86.1201102169668; Wed, 23 Jan 2008 07:29:29 -0800 (PST) Received: by 10.141.193.13 with HTTP; Wed, 23 Jan 2008 07:29:29 -0800 (PST) Message-ID: <9c1614e00801230729w508f309yada1272e499dff23@mail.gmail.com> Date: Wed, 23 Jan 2008 15:29:29 +0000 From: "Aldas Nabazas" To: freebsd-stable@freebsd.org In-Reply-To: <200801230919.23681.jhb@freebsd.org> MIME-Version: 1.0 References: <9c1614e00801200608k49195944mf241b7b0aa6a48@mail.gmail.com> <20080120175819.GA52965@owl.midgard.homeip.net> <35cWA$Gqi5kHFAjh@wood2.org.uk> <200801230919.23681.jhb@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Re: Dell Perc 6 disk geometry problem with RAID5 (both 6.3 final and 7.0 RC1) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Jan 2008 15:29:30 -0000 On Jan 23, 2008 2:19 PM, John Baldwin wrote: > On Sunday 20 January 2008 01:53:30 pm David Wood wrote: > > Hi there, > > > > In message <20080120175819.GA52965@owl.midgard.homeip.net>, Erik > > Trulsson writes > > >On Sun, Jan 20, 2008 at 04:48:56PM +0000, David Wood wrote: > > >> In message <9c1614e00801200608k49195944mf241b7b0aa6a48@mail.gmail.com > >, > > >> Aldas Nabazas writes > > >>> We bought a new Dell PowerEdge 2950III with Perc 6/i and have the > disk > > >>> geometry problem using 6.3 final or 7.0 RC1. Seems that we are not > alone at > > >>> least one guy has similar problem reported earlier: > > >>> > > >>> > http://unix.derkeiler.com/Mailing-Lists/FreeBSD/questions/2008-01/msg0 > > >>>0506.html > > > > > >I do not know if the mfi(4) driver has any problems with large disks, > but it > > >is however well known that fdisk(8) and bsdlabel(8) (the tools normally > used > > >to partition disks) have problems with volumes larger than 2TB. > > > > > >If you want to use volumes larger than 2TB then gpt(8) is the > recommended > > >way to partition the disks. It is however doubtful if the BIOS in your > > >system will allow you to boot from a gpt(8) parttioned volume which is > > >best solved with having a separate - smaller - boot volume where the OS > > >itself is installed. > > > > Erik's reminder is timely for those with >2TB volumes. > > > > You must use gpt and not fdisk on any disk, be it a single drive (in the > > future, at least!) or a virtual disk on a RAID setup that are bigger > > than 2TB. It may be wise to use gpt on any virtual disk that you might > > grow to 2TB or larger in the future, so long as you're not needing to > > boot from that virtual disk. > > > > fdisk will not work properly with 2TB and larger volumes - the MBR / > > partition table setup can't cope with these large volumes. > > > > > > You can't boot from a GPT volume - that's a limitation of the BIOS > > architecture. There is some thought about using EFI on x64 hardware in > > the future (EFI is used on ia64 hardware; GPT is part of EFI), but we're > > not there yet. This isn't just about adding GPT support to the BIOS - > > the whole BIOS setup is wedded to MBR. > > > > If you need to boot from a >2TB array, create two virtual disks - one > > smaller than 2TB to boot from (and use MBR on that), then the residue > > can be GPT. > > Actually, using gptboot in HEAD you can now boot from GPT on large volumes > (I've booted from a > 2 TB volume on a PERC5 using mfi(4) with it). I > will see about getting that merged back to 6.x and 7.x in CVS. We use > it for large volumes on 6.x and all volumes on 7.x at work. > > > When I said there was nothing relevant waiting for MFC, I was aware of > > the change that Tom mentioned, but that seems to be about Dell PERC 6 > > being identified as such rather than a MegaRAID. It doesn't seem that it > > will change the behaviour of the driver in any way. > > In our testing at work the 2950 rev 3's worked fine with mfi(4). > > -- > John Baldwin > Hi John, Nice to hear that. Regards, Aldas