On 09/27/2011 08:10 PM, Dave Chinner wrote:
I'm pretty sure this was fixed in 2.6.37. There's nothing wrong with
the filesystem, just the kernel code had an arbitrary restriction on
where inodes code be read from in 32-bit inode mode. That was
removed in commit d276734 ("xfs: fix bogus m_maxagi check in
xfs_iget").
OK, great. I'll be moving the system to kernel 3.0 soon.
xfs_reno is a tool designed to move all 64 bit inodes back into the
32 bit inode space again.
http://xfs.org/index.php/Unfinished_work#The_xfs_reno_tool
I'll give this a shot first.
Thanks for the pointers.
_______________________________________________
xfs mailing list
xfs@xxxxxxxxxxx
http://oss.sgi.com/mailman/listinfo/xfs
