From owner-freebsd-fs@FreeBSD.ORG Wed Dec 12 07:54:06 2007 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C75A216A417; Wed, 12 Dec 2007 07:54:06 +0000 (UTC) (envelope-from bvowk@math.ualberta.ca) Received: from 3jane.math.ualberta.ca (3jane.math.ualberta.ca [129.128.206.44]) by mx1.freebsd.org (Postfix) with ESMTP id 90F3813C447; Wed, 12 Dec 2007 07:54:06 +0000 (UTC) (envelope-from bvowk@math.ualberta.ca) Received: from 3jane.math.ualberta.ca (localhost.math.ualberta.ca [127.0.0.1]) by 3jane.math.ualberta.ca (8.14.1/8.13.8) with ESMTP id lBC7ZT3H054111; Wed, 12 Dec 2007 00:35:29 -0700 (MST) (envelope-from bvowk@math.ualberta.ca) Received: from localhost (bvowk@localhost) by 3jane.math.ualberta.ca (8.14.1/8.13.8/Submit) with ESMTP id lBC7ZThr054108; Wed, 12 Dec 2007 00:35:29 -0700 (MST) (envelope-from bvowk@math.ualberta.ca) X-Authentication-Warning: 3jane.math.ualberta.ca: bvowk owned process doing -bs Date: Wed, 12 Dec 2007 00:35:29 -0700 (MST) From: Barkley Vowk To: Ivan Voras In-Reply-To: Message-ID: <20071212003235.G54053@3jane.math.ualberta.ca> References: <475D7866.1070803@hangwithme.com> <475D7D60.4040701@fuckner.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-fs@freebsd.org, freebsd-hardware@freebsd.org Subject: Re: large disk > 8 TB X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Dec 2007 07:54:07 -0000 On Tue, 11 Dec 2007, Ivan Voras wrote: > Michael Fuckner wrote: >> Lan Tran wrote: >>> However, after I created a zfs zpool on this device it only shows 185 >>> GB. # zpool create tank /dev/mfid1s1d >>> # zpool list >>> NAME SIZE USED AVAIL CAP HEALTH ALTROOT >>> tank 185G 111K 185G 0% ONLINE - > This is the wrong way around. Why would something wrap drive sizes at a > 32-bit limit? The driver and the GEOM systems are 64-bit clean, if this > is a problem in ZFS, it's a serious one. It looks like he created a 32bit disk label. He needs to use either the raw device, or gpt partitions I think. Ie. /dev/mdid1 or /dev/mdid1p1 instead of /dev/mdid1s1