public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Ben Myers <bpm@sgi.com>
To: Stefan Priebe - Profihost AG <s.priebe@profihost.ag>
Cc: "xfs@oss.sgi.com" <xfs@oss.sgi.com>
Subject: Re: 32bit apps and inode64
Date: Fri, 15 Feb 2013 15:46:53 -0600	[thread overview]
Message-ID: <20130215214653.GP22182@sgi.com> (raw)
In-Reply-To: <511E4F00.2010703@profihost.ag>

Hi Stefan,

On Fri, Feb 15, 2013 at 04:06:40PM +0100, Stefan Priebe - Profihost AG wrote:
> i've discovered some problems on a host with a disk > 1TB. We've some
> binary 32bit applications which are not able to read some directory
> anymore after we've formated and installed the system using vanilla
> 3.7.7 kernel.
> 
> Right now we're using 3.0.61 kernel on this host - so 64bit apps work
> well and newly created files get 32bit inode numbers as inode64 is not
> the default.
> 
> Is there a way to find / get all 64bit inode files / dies and convert
> them back to 32bit without a reinstall?

On IRIX you could use xfs_reno to renumber those inodes.
http://techpubs.sgi.com/library/tpl/cgi-bin/getdoc.cgi?coll=0650&db=man&fname=/usr/share/catman/a_man/cat1/xfs_reno.z

xfs_reno was ported to linux in '07 and was most recently reposted by Jeff Liu:
http://oss.sgi.com/archives/xfs/2012-11/msg00425.html

It isn't in xfsprogs today.

Regards,
	Ben

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

  reply	other threads:[~2013-02-15 21:46 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-06  9:01 suddenly slow writes on XFS Filesystem Stefan Priebe
2012-05-06 10:31 ` Martin Steigerwald
2012-05-06 10:33 ` Martin Steigerwald
2012-05-06 15:45   ` Stan Hoeppner
2012-05-06 19:25     ` Stefan Priebe
2012-05-07  1:39       ` Dave Chinner
2012-05-06 21:43     ` Martin Steigerwald
2012-05-07  6:40       ` Stefan Priebe - Profihost AG
2012-05-07  1:34 ` Dave Chinner
2012-05-07  6:39   ` Stefan Priebe - Profihost AG
2012-05-07  7:17     ` Dave Chinner
2012-05-07  7:22       ` Stefan Priebe - Profihost AG
2012-05-07 16:36         ` Stan Hoeppner
2012-05-07 19:08           ` Martin Steigerwald
2012-05-07 20:05           ` Stefan Priebe
2012-05-09  6:57             ` Stan Hoeppner
2012-05-09  7:04               ` Dave Chinner
2012-05-09  7:36                 ` Stefan Priebe - Profihost AG
2012-05-09  7:49                 ` Stan Hoeppner
2013-02-15 15:06                 ` 32bit apps and inode64 Stefan Priebe - Profihost AG
2013-02-15 21:46                   ` Ben Myers [this message]
2013-02-16 10:24                     ` Stefan Priebe - Profihost AG
2013-02-17 21:33                       ` Dave Chinner
2013-02-18  8:12                         ` Stefan Priebe - Profihost AG
2013-02-18 22:06                           ` Dave Chinner
2013-02-17  8:13                     ` Jeff Liu
2013-02-19 19:11                       ` Ben Myers
2012-05-07 23:42         ` suddenly slow writes on XFS Filesystem Dave Chinner
2012-05-07  8:21     ` Martin Steigerwald
2012-05-07 16:44       ` Stan Hoeppner
2012-05-07  8:31     ` Martin Steigerwald
2012-05-07 13:57       ` Stefan Priebe - Profihost AG
2012-05-07 14:32         ` Martin Steigerwald

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=20130215214653.GP22182@sgi.com \
    --to=bpm@sgi.com \
    --cc=s.priebe@profihost.ag \
    --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