[Top] [All Lists]

Re: [PATCH] enable inode64 by default when possible

To: xfs@xxxxxxxxxxx
Subject: Re: [PATCH] enable inode64 by default when possible
From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
Date: Fri, 09 Apr 2010 21:37:44 -0500
In-reply-to: <1270850499.7840.25.camel@doink>
References: <4B7309D7.5090800@xxxxxxxxxxx> <1270850499.7840.25.camel@doink>
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv: Gecko/20100317 Thunderbird/3.0.4
Alex Elder put forth on 4/9/2010 5:01 PM:

> OK, it's been about two months since Eric proposed this, and
> I'm finally getting around to writing up a response.
> I discussed this with a few people within SGI, and there were
> two main concerns that were mentioned:
> - This may be a problem for some NFS clients
> - This may be a problem for some backup software
> We don't believe there are any direct issues with DMF or CXFS
> in making this change.
> I understand that the change is only in the default behavior,
> and that forcing 32-bit inodes will still be an available
> option.

Hi Alex,

How will this change affect those people running 32bit CPUs and kernels, if
at all?  Or is this change related not to the word width of the hardware/OS
but to the size of the filesystem and/or number of files/inodes contained
within?  You mentioned possible issues with NFS.  Are there any issues with

Intel Atom (32bit x86) CPUs and XFS on multi terabyte disks are popular with
many folks running Linux based media PCs, streaming their ripped DVDs and
other large media files from their XFS filesystems.  I don't personally do
this, but I also have 32bit only systems that won't be replaced with 64bit
CPUs for some time to come.



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