From: Michael Cronenworth <mike@cchtml.com>
To: Dave Chinner <david@fromorbit.com>
Cc: xfs@oss.sgi.com
Subject: Re: 64-bit inodes and back again
Date: Tue, 27 Sep 2011 20:31:04 -0500 [thread overview]
Message-ID: <4E8278D8.9060309@cchtml.com> (raw)
In-Reply-To: <20110928011020.GE3159@dastard>
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@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2011-09-28 1:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-27 23:28 64-bit inodes and back again Michael Cronenworth
2011-09-28 1:10 ` Dave Chinner
2011-09-28 1:31 ` Michael Cronenworth [this message]
2011-09-28 2:52 ` Michael Cronenworth
2011-09-28 5:35 ` Dave Chinner
2011-09-28 6:58 ` Michael Cronenworth
2011-09-28 11:07 ` Dave Chinner
2011-09-28 13:13 ` Michael Cronenworth
2011-09-28 17:37 ` Stan Hoeppner
2011-09-28 18:05 ` Michael Cronenworth
2011-09-29 0:25 ` Dave Chinner
2011-09-29 0:37 ` Michael Cronenworth
2011-09-28 5:48 ` Michael Monnerie
2011-09-28 6:55 ` Michael Cronenworth
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4E8278D8.9060309@cchtml.com \
--to=mike@cchtml.com \
--cc=david@fromorbit.com \
--cc=xfs@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox