From owner-freebsd-questions Fri Dec 14 12:58:20 2001 Delivered-To: freebsd-questions@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by hub.freebsd.org (Postfix) with ESMTP id 1D9BB37B405; Fri, 14 Dec 2001 12:58:15 -0800 (PST) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.6/8.11.6) with ESMTP id fBEKt7u27329; Fri, 14 Dec 2001 21:55:07 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: David Greenman Cc: Bernd Walter , John Reynolds~ , questions@FreeBSD.ORG, fs@FreeBSD.ORG Subject: Re: off_t governs the largest file size, correct? In-Reply-To: Your message of "Fri, 14 Dec 2001 12:22:24 PST." <20011214122224.E81485@nexus.root.com> Date: Fri, 14 Dec 2001 21:55:07 +0100 Message-ID: <27327.1008363307@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <20011214122224.E81485@nexus.root.com>, David Greenman writes: >>8k blocksize works up to 8TB on alpha-current: >>ticso@cicely9# ls -al test >>-rw-r--r-- 1 root wheel 8388609048576 Dec 14 20:50 test >> >>I have tried 9000000 MB which failed. >> >>But keep in mind that the maximum size of a single filesystem is still >>1TB, which restricts you to use sparse files. > > Actually, the largest device size that FreeBSD (at least x86) supports >is 1TB. This is because daddr_t (the type used to specify physical disk >block addresses) is a signed int, which is 31bits worth of 512 byte blocks. This will be changed to 2^64 bytes as part of the DARPA contract I'm working on. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message