From: Andreas Dilger Subject: Re: fscache review comments, part 1 Date: Thu, 28 Sep 2006 11:30:17 -0600 Message-ID: <20060928173017.GE22010@schatzie.adilger.int> References: <20060928164529.GA3497@infradead.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: dhowells@redhat.com, akpm@osdl.org, linux-fsdevel@vger.kernel.org Return-path: Received: from mail.clusterfs.com ([206.168.112.78]:23201 "EHLO mail.clusterfs.com") by vger.kernel.org with ESMTP id S1751958AbWI1RaT (ORCPT ); Thu, 28 Sep 2006 13:30:19 -0400 To: Christoph Hellwig Content-Disposition: inline In-Reply-To: <20060928164529.GA3497@infradead.org> Sender: linux-fsdevel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org On Sep 28, 2006 17:45 +0100, Christoph Hellwig wrote: > 02-ino64-nfs.diff: > Unfortunately there's a lot of broken userspace that can't deal > with 64bit inode numbers, so you need to make the lod behaviour > a mount option at least, probably even the default. Given that > we're going to run into problems like that it might make sense > to make the option VFS-level instead of just in nfs. (Note: > XFS already has an option like that) A general question - is there a known list of common applications that have problems with 64-bit inodes? It's been mentioned several times, but I'm wondering if any effort is going toward fixing those apps so that 5 years from now (or whenever) we CAN have 64-bit inodes. If it relates to on-disk formats like ustar, we can always work with something like star to ensure that it is useful in the future. Cheers, Andreas -- Andreas Dilger Principal Software Engineer Cluster File Systems, Inc.