From: Dave Chinner <david@fromorbit.com>
To: Michael Cronenworth <mike@cchtml.com>
Cc: xfs@oss.sgi.com
Subject: Re: 64-bit inodes and back again
Date: Wed, 28 Sep 2011 11:10:20 +1000 [thread overview]
Message-ID: <20110928011020.GE3159@dastard> (raw)
In-Reply-To: <4E825C25.6050804@cchtml.com>
On Tue, Sep 27, 2011 at 06:28:37PM -0500, Michael Cronenworth wrote:
> Hello,
>
> I enabled 64-bit inodes on a 2.6.35.14 kernel system. I ran into
> some software that did not handle this well, so I wanted to go back
> to 32-bit inodes. When I booted into the system again, any files
> that were created while in 64-bit inode mode are inaccessable and
> are shown to me like this:
>
> $ ls -l /var/lib/mock/
> ls: cannot access /var/lib/mock/dist-5E-build-373-1401: Invalid argument
> ??????????? ? ? ? ? ? dist-5E-build-373-1401
>
> I was led[1] to believe that this would not cause problems, but it has.
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").
> I have run xfs_repair on the file system but the old files still remain.
>
> Are there any other things I can do to fix this? One thought is to
> remount with 64-bit inodes and erase or copy the offending files,
> but is that my only option?
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
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2011-09-28 1:10 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 [this message]
2011-09-28 1:31 ` Michael Cronenworth
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=20110928011020.GE3159@dastard \
--to=david@fromorbit.com \
--cc=mike@cchtml.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