xfs
[Top] [All Lists]

Re: Work Items

To: Alp ATICI <atici@xxxxxxxxxxxxxxxxxxxxx>
Subject: Re: Work Items
From: Stephen Lord <lord@xxxxxxx>
Date: 12 Oct 2002 15:42:33 -0500
Cc: Christoph Hellwig <hch@xxxxxxxxxxxxx>, linux-xfs@xxxxxxxxxxx
In-reply-to: <Pine.LNX.4.44.0210121124180.26350-100000@xxxxxxxxxxxxxxxxxxxxx>
References: <Pine.LNX.4.44.0210121124180.26350-100000@xxxxxxxxxxxxxxxxxxxxx>
Sender: linux-xfs-bounce@xxxxxxxxxxx
On Sat, 2002-10-12 at 10:36, Alp ATICI wrote:
> On Sat, 12 Oct 2002, Christoph Hellwig wrote:
> 
> > XFS does have 64bit inodes, Linux VFS doesn't.
> 
> Hmm but check this:
> http://marc.theaimsgroup.com/?l=linux-xfs&m=100740237824601&w=2
> (TAKE - restrict xfs inodes to 32 bits)
> 
> http://marc.theaimsgroup.com/?l=linux-xfs&m=99928901910853&w=2
> (TAKE - mkfs/growfs 32-bit inode number awareness)
> 
> Now are these restrictions going to be released after the latest 2.5
> kernel (that includes Peter Chubb's 64-bit patches that removes 2TB
> limit)? or that doesn't mean Linux VFS supports 64 bit inodes still?
> Alp
> 

The 2 Tbyte limit and 32 bit inodes are totally different things.
The 32 bit inode number issue can be solved internally within
the kernel, until you get to system calls, and a number of system
calls want to make an inode number available to user space. Right
now there is no room in the structures returned from these calls
for 64 bits of inode space.

In order for xfs to function beyond the 2 Tbyte limit, all we need
to do is enable large filesystem support again in XFS. This is a
one character change. In xfs_types.h define XFS_BIG_FILESYSTEMS to
1 instead of zero.

Steve



<Prev in Thread] Current Thread [Next in Thread>