From owner-freebsd-current@FreeBSD.ORG Mon Jun 6 15:51:05 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E8F0316A41C; Mon, 6 Jun 2005 15:51:05 +0000 (GMT) (envelope-from scottl@pooker.samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3529F43D1F; Mon, 6 Jun 2005 15:51:04 +0000 (GMT) (envelope-from scottl@pooker.samsco.org) Received: from pooker.samsco.org (localhost [127.0.0.1]) by pooker.samsco.org (8.13.3/8.13.3) with ESMTP id j56Fv5Hu053010; Mon, 6 Jun 2005 09:57:05 -0600 (MDT) (envelope-from scottl@pooker.samsco.org) Received: from localhost (scottl@localhost) by pooker.samsco.org (8.13.3/8.13.1/Submit) with ESMTP id j56Fv4Ws053007; Mon, 6 Jun 2005 09:57:04 -0600 (MDT) (envelope-from scottl@pooker.samsco.org) Date: Mon, 6 Jun 2005 09:57:04 -0600 (MDT) From: Scott Long To: =?iso-8859-1?q?Dag-Erling_Sm=F8rgrav?= In-Reply-To: <86fyvvqzil.fsf@xps.des.no> Message-ID: <20050606095117.Q52957@pooker.samsco.org> References: <82ACAD58-B179-44E2-852F-60F25C0BBBC1@FreeBSD.org> <20050606033145.GA80739@www.portaone.com> <42A3D6CF.2000504@samsco.org> <0A6C1F19-A734-4EC8-BE97-2D000D189968@FreeBSD.org> <42A453B5.3020006@samsco.org> <86oeaj1r2x.fsf@xps.des.no> <42A463EF.5060401@samsco.org> <86fyvvqzil.fsf@xps.des.no> MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-123071739-1118073379=:52957" X-Spam-Status: No, score=-2.8 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on pooker.samsco.org X-Mailman-Approved-At: Tue, 07 Jun 2005 12:24:14 +0000 Cc: Suleiman Souhlal , Garance A Drosihn , current@freebsd.org, fs@freebsd.org Subject: Re: [PATCH] IFS: Inode FileSystem X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Jun 2005 15:51:06 -0000 This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --0-123071739-1118073379=:52957 Content-Type: TEXT/PLAIN; charset=iso-8859-1; format=flowed Content-Transfer-Encoding: QUOTED-PRINTABLE On Mon, 6 Jun 2005, [iso-8859-1] Dag-Erling Sm=F8rgrav wrote: > Scott Long writes: >> Dag-Erling Sm=F8rgrav wrote: >>> This is primarily an API issue, not a filesystem layout issue. We >>> already have at least one filesystem with 64-bit inodes (msdosfs). >> What do you mean it's not a layout issue? We can't make incompatible >> layout changes whever we feel like it, or else transportability of >> filesystems is completely lost and everyone who wants to boot more >> than just the Last And Greatest on their system winds up with >> unnessary pain. > > Changing the stat(2) API to support 64-bit inodes does not require us > to simultaneously change the on-disk layout of every filesystem we > support to use 64-bit inodes. However, if we want to fully support > filesystems with 64-bit inodes (such as FAT32, which currently uses a > convoluted hack to map the 64-bit offset of a directory entry into a > 32-bit inode), we need to change the API. > > The ironic thing is that we already have a 64-bit stat(2)... for > Linux ABI compatibility. > Ah, I see your point. Well, it's not too late to address this for 6.0, and it might be a really good idea to think about it now. Is there=20 anything else that should be bumped along with it? Scott --0-123071739-1118073379=:52957--