From owner-freebsd-current@FreeBSD.ORG Wed Feb 16 23:02:59 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 11B2616A4CE for ; Wed, 16 Feb 2005 23:02:59 +0000 (GMT) Received: from mh1.centtech.com (moat3.centtech.com [207.200.51.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6CC7543D45 for ; Wed, 16 Feb 2005 23:02:58 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from [10.177.171.220] (neutrino.centtech.com [10.177.171.220]) by mh1.centtech.com (8.13.1/8.13.1) with ESMTP id j1GN2vkc097526; Wed, 16 Feb 2005 17:02:58 -0600 (CST) (envelope-from anderson@centtech.com) Message-ID: <4213D099.3020504@centtech.com> Date: Wed, 16 Feb 2005 17:00:41 -0600 From: Eric Anderson User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.5) Gecko/20050210 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Brooks Davis References: <20050216215325.9201.qmail@web26805.mail.ukl.yahoo.com> <4213C1FB.6030802@centtech.com> <20050216225528.GB2787@odin.ac.hmc.edu> In-Reply-To: <20050216225528.GB2787@odin.ac.hmc.edu> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.82/707/Wed Feb 16 16:00:07 2005 on mh1.centtech.com X-Virus-Status: Clean cc: FreeBSD Current Subject: Re: newfs limits? 10TB filesystem max? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Feb 2005 23:02:59 -0000 Brooks Davis wrote: > On Wed, Feb 16, 2005 at 03:58:19PM -0600, Eric Anderson wrote: > >>Claus Guttesen wrote: >> >>>>I've just built an enormous 10TB filesystem. When >>>>trying to newfs the disk, it bombed with something >>>>like "cannot allocate memory" after something like >>>>23xxxxxxxxx sectors.. I noticed disklabel complains >>>>about disks with more than 2^32-1 sectors not being >>>>supported.. >>> >>> >>>Aren't you supposed to use gpt(8) to define partitions >>>larger than 2 TB? >> >>No idea - this is the first I've heard of gpt really.. >> >> >> >>>>Is newfs supposed to be able to work? I've used the >>>>-s option to newfs to limit my filesystem size to >>>>the max it would allow, which ends up being >>>>11350482546 1K blocks, which means I'm only losing a >>>>couple GB, which is no sweat right now for me, but >>>>if someone wanted a 20TB filesystem, they'd be >>>>hosed. >>> >>> >>>Then the question is whether newfs reads >>>gpt-partitioned disks? From newfs(8): >>> >>>Before running newfs the disk must be labeled using >>>bsdlabel(8). >>> >>>How did you create such a huge partition? Your >>>question is quite interesting, I'm at a >>>storage-solution which supports LUN's larger than 2.2 >>>TB. >> >>I used vinum to stripe 6 2TB partitions connected to 2 fiber channel disk >>arrays. Vinum automatically does the bsdlabel part. I was merely wanting >>to see what bsdlabel had to say about the vinum disk (if anything). >> >>Using newfs on it worked as long as I specified a smaller sector count. > > > bsdlabels are for the most part unable to access more then 2TB of > storage. You should either newfs the disk directly or use gpt. If > vinum is creating a bsdlabel, the label is almost certaintly bogus if > the disk is larger than 2TB. There is an exception if the disk has > sectors larger than 512K, but those are fairly rare. Hmm - well, it works.. :) Is there something I should be aware of that I'm not seeing? If anyone is interested in any stats, or other info, please let me know. I can provide any details if anyone is curious.. Eric -- ------------------------------------------------------------------------ Eric Anderson Sr. Systems Administrator Centaur Technology I have seen the future and it is just like the present, only longer. ------------------------------------------------------------------------