From owner-freebsd-hackers Mon Oct 9 14:11:14 1995 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id OAA23261 for hackers-outgoing; Mon, 9 Oct 1995 14:11:14 -0700 Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id OAA23256 for ; Mon, 9 Oct 1995 14:11:10 -0700 Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id OAA09048; Mon, 9 Oct 1995 14:08:07 -0700 From: Terry Lambert Message-Id: <199510092108.OAA09048@phaeton.artisoft.com> Subject: Re: 52gb RAID, works, sorta. To: henrich@crh.cl.msu.edu (Charles Henrich) Date: Mon, 9 Oct 1995 14:08:07 -0700 (MST) Cc: terry@lambert.org, freebsd-hackers@FreeBSD.ORG In-Reply-To: <199510090104.VAA16572@crh.cl.msu.edu> from "Charles Henrich" at Oct 8, 95 09:04:09 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 877 Sender: owner-hackers@FreeBSD.ORG Precedence: bulk > > There is an explicit limitation on file size because of the paging code. > > So then is b_avail the max size of a file, and not the available blocks on the > device? I.e. even though it reports 4gb, I should be able to place >4gb of > files there? No. The b_avail is incorrectly calculated, per the last posting. You can have more than 4G of files but no more than a 2G file if you correct the 4-6 places where the calculation is incorrect. Even then, there's a 39 and 41 bit limitation on disk size in several more places. The 2G file size limit can be pushed to 4G, but that assumes you fix the sign extension issues on the quad for -1 returns from lseek and use of the sign bit for indirect blocks (in the UFS code itself). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.