From owner-freebsd-hackers Sun Feb 25 15:37:51 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from earth.backplane.com (earth-nat-cw.backplane.com [208.161.114.67]) by hub.freebsd.org (Postfix) with ESMTP id 6DBAA37B4EC for ; Sun, 25 Feb 2001 15:37:49 -0800 (PST) (envelope-from dillon@earth.backplane.com) Received: (from dillon@localhost) by earth.backplane.com (8.11.2/8.9.3) id f1PNbeS18875; Sun, 25 Feb 2001 15:37:40 -0800 (PST) (envelope-from dillon) Date: Sun, 25 Feb 2001 15:37:40 -0800 (PST) From: Matt Dillon Message-Id: <200102252337.f1PNbeS18875@earth.backplane.com> To: Bernd Walter Cc: David Gilbert , Bernd Walter , freebsd-hackers@FreeBSD.ORG Subject: Re: [hackers] Re: Large MFS on NFS-swap? References: <15000.8884.6165.759008@trooper.velocet.net> <20010225042933.A508@cicely5.cicely.de> <200102250644.f1P6iuL12016@earth.backplane.com> <15001.21129.307283.198917@trooper.velocet.net> <200102251913.f1PJDAc15495@earth.backplane.com> <15001.35517.468307.915125@trooper.velocet.net> <20010226001436.A728@cicely8.cicely.de> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :With 512 Byte blocksizes you are limited to 1T because the physical :block number is a signed 32bit. :FFS uses 32bit (I wouldn't count on the high bit) frag numbers. :A fragment defaults to 1k so even with 1k fragments the limit is :at least 2T. Yes, the FFS limit is essentially the frag size limitation. However, internally our device I/O path normalizes blocks to 512 byte quantities. I've heard of people running larger filesystems (16TB) with larger fragment sizes, but I'm not exactly sure how it can work under FreeBSD due to the normalization that the FreeBSD device layer makes. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message