From owner-freebsd-bugs Wed May 10 12:50: 6 2000 Delivered-To: freebsd-bugs@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 6A4BB37B93E for ; Wed, 10 May 2000 12:50:04 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id MAA04049; Wed, 10 May 2000 12:50:03 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Date: Wed, 10 May 2000 12:50:03 -0700 (PDT) Message-Id: <200005101950.MAA04049@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: David Greenman Subject: Re: bin/18485: Dont let filesys go over 4G if not supported Reply-To: David Greenman Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR bin/18485; it has been noted by GNATS. From: David Greenman To: boxiao63@hotmail.com Cc: freebsd-gnats-submit@FreeBSD.ORG Subject: Re: bin/18485: Dont let filesys go over 4G if not supported Date: Wed, 10 May 2000 12:36:39 -0700 >>Description: >Since 32 bit couter only go as high as 4.2G, no filesys over >that size should be allowed. With today's disk size, users >will attempt to do just that. Either labeling or newfs should >catch it. > >Many unexpected/unpredictable error happen when using the fs >portion beyond a 32 bit counter can count. There are many production filesystems that are much much larger than that and have no problems. Can you be more specific about the trouble you are having? FreeBSD uses 64bit ints to store things that can be larger than 32bits. -DG David Greenman Co-founder, The FreeBSD Project - http://www.freebsd.org Creator of high-performance Internet servers - http://www.terasolutions.com Pave the road of life with opportunities. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message