|To:||Dave Chinner <david@xxxxxxxxxxxxx>|
|Subject:||Re: 64-bit inodes and back again|
|From:||Michael Cronenworth <mike@xxxxxxxxxx>|
|Date:||Tue, 27 Sep 2011 20:31:04 -0500|
|User-agent:||Mozilla/5.0 (X11; Linux x86_64; rv:6.0.2) Gecko/20110906 Thunderbird/6.0.2|
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.
|<Prev in Thread]||Current Thread||[Next in Thread>|
|Previous by Date:||Re: 64-bit inodes and back again, Dave Chinner|
|Next by Date:||Re: 64-bit inodes and back again, Michael Cronenworth|
|Previous by Thread:||Re: 64-bit inodes and back again, Dave Chinner|
|Next by Thread:||Re: 64-bit inodes and back again, Michael Cronenworth|
|Indexes:||[Date] [Thread] [Top] [All Lists]|