From owner-freebsd-questions@FreeBSD.ORG Tue Jul 19 22:09:16 2005 Return-Path: X-Original-To: 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 3668416A41F for ; Tue, 19 Jul 2005 22:09:16 +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 E2B7F43D48 for ; Tue, 19 Jul 2005 22:09:15 +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 j6JM9FrR097934 for ; Tue, 19 Jul 2005 15:09:15 -0700 (PDT) Received: from localhost (dpk@localhost) by shared10.hosting.flyingcroc.net (8.12.9p2/8.12.10/Submit) with ESMTP id j6JM9EWP097931 for ; Tue, 19 Jul 2005 15:09:15 -0700 (PDT) X-Authentication-Warning: shared10.hosting.flyingcroc.net: dpk owned process doing -bs Date: Tue, 19 Jul 2005 15:09:14 -0700 (PDT) From: dpk X-X-Sender: dpk@shared10.hosting.flyingcroc.net To: questions@freebsd.org Message-ID: <20050719145822.W23753@shared10.hosting.flyingcroc.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: Subject: 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: Tue, 19 Jul 2005 22:09:16 -0000 Has anyone here had any luck whatsoever getting FreeBSD 5.4-RELEASE to use 4TB of space from a 4TB RAID array? It is apparent that there is a 1TB/slice limit, and sysinstall doesn't seem to be able to handle creating more than 2 slices. I read somewhere that people recommend using "gpt" to manage large filesystems. Unfortunately, this tool is not to be found on the fixit floppy or the mfsroot during installation. If the server is up, gpt complains about "Operation not permitted" because the disk is in use. I managed to get "gpt" on a floppy -- along with a hand written cp/mkdir all-in-one binary because, when you use the "Fixit" option it does not chroot you to the fixit floppy, meaning you'll need /libexec/ld-elf.so.1 and /lib/libc.so.5, because for some reason critical system utilities are built dynamically now.... but I am straying from the topic -- and ran "gpt migrate" as recommended in its man page. Now gpt no longer recognizes the the disk at all. gpt show fails entirely. gpt -vvv show lists some entries, but the sizes are all very wrong, as if they were truncated. Anyone know the specific tricks involved in getting all 4TB used, even if it has to be in 4 different slices, or am I stuck with using just 2TB? We're gonna have to go with Linux on this particular server since we need it up today but we'll be getting another one soon and I can try things there.