free inodes remaining in 1tb

[Keith Keller]

Thank you both Dave and Carlos for your replies.  My response inline.

On Fri, Sep 27, 2013 at 11:08:47AM +1000, Dave Chinner wrote:
> On Thu, Sep 26, 2013 at 03:47:00PM -0700, Keith Keller wrote:
> 
> > so that I can plan for a migration to
> > inode64 (if it's very few, I would make it a high priority; if not, it
> > can be done in a few weeks instead, for example).  Is there an easy
> > way (or even a hard way) to query the filesystem for this information?
> 
> Only a hard way - using xfs_db to look at on-disk structures and
> inferring the state from there...

That's what I was afraid of.  :)

> So if you have an old kernel (older than 2.6.35), you won't be able
> to access 64 bit inodes at all if you mount with inode32. Anything
> more recent than that will work just fine.

I am currently using a stock CentOS kernel, 2.6.32-358.14.1.el6.x86_64.
I'd have to check the changelogs to see if that kernel has the patch
in question, which I will do tomorrow.  I have another machine on
kernel-ml which I'm trying out now, and may simply move the original
machine to it as well.

> The inode number is an encoding of the physical location of the inod
> inthe filesystem. Hence the kernel code can always find the inode
> location - it just may not be able to do anything with it because
> the caches on old kernels can't index them...

Great, thanks, that's really helpful.

On 2013-09-26, Carlos Maiolino <cmaiolino at redhat.com> wrote:
> bear in mind though that are some applications that can't read 64bit
> inodes.

I know that NFS has some issues (documented in the XFS FAQ).  Do you
know offhand of any other examples?

--keith


-- 
kkeller at wombat.san-francisco.ca.us