From: Christoph Hellwig <hch@infradead.org>
To: Michael Weissenbacher <mw@dermichi.com>
Cc: xfs@oss.sgi.com
Subject: Re: regarding the inode64 mount option
Date: Thu, 28 May 2009 10:56:15 -0400 [thread overview]
Message-ID: <20090528145612.GA14684@infradead.org> (raw)
In-Reply-To: <4A1E81D8.7010706@dermichi.com>
On Thu, May 28, 2009 at 02:21:44PM +0200, Michael Weissenbacher wrote:
> Hi XFS-List!
> I understand that the inode64 mount option allows inodes to be created beyond 1TB. There are also certain performance problems that can be cured by using this option when handling LOTS of inodes. During my tests i noticed that enabling it is like a one-way street. Inodes created with inode64 enabled aren't accessible when the option is left out.
Actually they should still be accessible, we just won't create new
inodes not addressable by 32bit inode numbers.
> Now i got a few questions:
> - Does the inode64 option work only on 64bit architectures or is it also possible to use it with i686
It is available for 32bit kernels starting with kernel 2.6.29.
> - Is there a way to convert the inodes back
There's an xfs_reno tool ported from IRIX to renumber the inodes. I'll
see if I can finally get it packaged.
> - Why doesn't the filesystem remember that inode64 was used in the past and enable it automatically
Good question. We could introduce a flag in the superblock for this.
> - Do i have to pass inode64 via grub / lilo if i want to use it on my root filesystem
Yes.
> I haven't found any definitive clear documentation abount the pro's and con's, so maybe you can give me some hints :-)
The only reason speaking against inode64 are old buggy programs that
can't cope with a 64bit ino_t, Eric had a quite scary list of those
in Fedora somewhere..
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2009-05-28 14:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-28 12:21 regarding the inode64 mount option Michael Weissenbacher
2009-05-28 14:56 ` Christoph Hellwig [this message]
2009-05-28 15:18 ` Eric Sandeen
2009-06-02 10:29 ` Michael Weissenbacher
2009-06-02 13:24 ` Felix Blyakher
2009-06-02 16:13 ` Felix Blyakher
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=20090528145612.GA14684@infradead.org \
--to=hch@infradead.org \
--cc=mw@dermichi.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