All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Cronenworth <mike@cchtml.com>
To: xfs@oss.sgi.com
Subject: 64-bit inodes and back again
Date: Tue, 27 Sep 2011 18:28:37 -0500	[thread overview]
Message-ID: <4E825C25.6050804@cchtml.com> (raw)

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 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?

[1] 
http://xfs.org/index.php/XFS_FAQ#Q:_Can_I_just_try_the_inode64_option_to_see_if_it_helps_me.3F

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

             reply	other threads:[~2011-09-27 23:28 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-27 23:28 Michael Cronenworth [this message]
2011-09-28  1:10 ` 64-bit inodes and back again Dave Chinner
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=4E825C25.6050804@cchtml.com \
    --to=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.