From owner-freebsd-questions@FreeBSD.ORG Fri Jul 29 16:27:13 2005 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0F02116A434 for ; Fri, 29 Jul 2005 16:27:13 +0000 (GMT) (envelope-from dpk@dpk.net) Received: from shared10.hosting.flyingcroc.net (shared10.hosting.flyingcroc.net [207.246.149.144]) by mx1.FreeBSD.org (Postfix) with ESMTP id A37CE43D4C for ; Fri, 29 Jul 2005 16:27:12 +0000 (GMT) (envelope-from dpk@dpk.net) Received: from shared10.hosting.flyingcroc.net (localhost [127.0.0.1]) by shared10.hosting.flyingcroc.net (8.12.9p2/8.12.10) with ESMTP id j6TGRCrR085876 for ; Fri, 29 Jul 2005 09:27:12 -0700 (PDT) Received: from localhost (dpk@localhost) by shared10.hosting.flyingcroc.net (8.12.9p2/8.12.10/Submit) with ESMTP id j6TGRBQc085873 for ; Fri, 29 Jul 2005 09:27:12 -0700 (PDT) X-Authentication-Warning: shared10.hosting.flyingcroc.net: dpk owned process doing -bs Date: Fri, 29 Jul 2005 09:27:11 -0700 (PDT) From: dpk X-X-Sender: dpk@shared10.hosting.flyingcroc.net cc: freebsd-questions@freebsd.org In-Reply-To: <20050729003005.GA99178@gothmog.gr> Message-ID: <20050729091412.V79761@shared10.hosting.flyingcroc.net> References: <20050719145822.W23753@shared10.hosting.flyingcroc.net> <441x5tk3e9.fsf@be-well.ilk.org> <20050720064637.Q23753@shared10.hosting.flyingcroc.net> <20050721100327.GA16179@beatrix.daedalusnetworks.priv> <20050728154356.A79761@shared10.hosting.flyingcroc.net> <20050728225701.GB46755@gothmog.gr> <20050728155804.T79761@shared10.hosting.flyingcroc.net> <20050728231035.GA60181@gothmog.gr> <20050728161608.Q79761@shared10.hosting.flyingcroc.net> <20050729003005.GA99178@gothmog.gr> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: Re: Large filesystem woes X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Jul 2005 16:27:13 -0000 The resolution to this problem turned out to be enabling the 3Ware 9500S "auto carving" option. This splits all partitions into 2TB chunks, which are then presented to the OS as separate LUNs. FreeBSD 5.4-RELEASE's driver for the 3Ware card does not support multiple LUNs, but the new driver (Common Layer) in 5.4-STABLE does. So if you're running in to this same problem, here's a quick run down of what you need to do: 1) Enable auto-carving in either the 3ware BIOS or in the 3dm web control panel. 2) Delete and then re-create any RAID that is larger than 2TB, that you want accessable from the OS. If you have sufficient drives available, you can migrate the data to a new RAID, instead of deleting. 3) Install 5.4-RELEASE. sysinstall will show you a single 2TB device. Feel free to use that device however you wish -- you can fill it to its boundaries. 4) cvsup to 5.4-STABLE, make buildworld buildkernel installkernel, reboot. 5) You'll now see da1 and perhaps da2 and beyond, in dmesg or camcontrol devlist. If you should ever have to reboot into the 5.4-RELEASE GENERIC kernel, the da1..n partitions will be unavailable. da0, however, will operate normally. As such it is safe to use as a boot device. (For sanity's sake it is probably best to create a much smaller slice or partition for system files, but that's your decision).