From: Joel Becker <Joel.Becker@oracle.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [PATCH 1/3] ocfs2: Limit inode allocation to 32bits.
Date: Thu, 4 Sep 2008 18:38:16 -0700 [thread overview]
Message-ID: <20080905013816.GA28061@mail.oracle.com> (raw)
In-Reply-To: <20080905002749.GA29097@lst.de>
On Fri, Sep 05, 2008 at 02:27:49AM +0200, Christoph Hellwig wrote:
> On Wed, Sep 03, 2008 at 08:03:39PM -0700, Joel Becker wrote:
> > ocfs2 inode numbers are block numbers. For any filesystem with less
> > than 2^32 blocks, this is not a problem. However, when ocfs2 starts
> > using JDB2, it will be able to support filesystems with more than 2^32
> > blocks. This would result in inode numbers higher than 2^32.
> >
> > The problem is that stat(2) can't handle those numbers on 32bit
> > machines. The simple solution is to have ocfs2 allocate all inodes
> > below that boundary.
>
> Actually stat64 which most apps should use handles it just fine, but
> there are various programs still around not using it.
Somehow I got the impression that some systems couldn't handle
inode64 at all. If it's just some userspace, that gives us more
flexibility.
Joel
--
Life's Little Instruction Book #3
"Watch a sunrise at least once a year."
Joel Becker
Principal Software Developer
Oracle
E-mail: joel.becker at oracle.com
Phone: (650) 506-8127
next prev parent reply other threads:[~2008-09-05 1:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-04 3:03 [Ocfs2-devel] [PATCH 0/3] ocfs2: Switch over to JBD2 Joel Becker
2008-09-04 3:03 ` [Ocfs2-devel] [PATCH 1/3] ocfs2: Limit inode allocation to 32bits Joel Becker
2008-09-05 0:27 ` Christoph Hellwig
2008-09-05 1:38 ` Joel Becker [this message]
2008-09-04 3:03 ` [Ocfs2-devel] [PATCH 2/3] ocfs2: Add the 'inode64' mount option Joel Becker
2008-09-05 0:29 ` Christoph Hellwig
2008-09-04 3:03 ` [Ocfs2-devel] [PATCH 3/3] ocfs2: Switch over to JBD2 Joel Becker
2008-09-05 0:32 ` Christoph Hellwig
2008-09-05 1:40 ` Joel Becker
2008-09-04 3:03 ` Joel Becker
2008-09-05 10:05 ` [Ocfs2-devel] [PATCH 0/3] " Mark Fasheh
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=20080905013816.GA28061@mail.oracle.com \
--to=joel.becker@oracle.com \
--cc=ocfs2-devel@oss.oracle.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.