From: Alexander Viro <aviro@redhat.com>
To: Theodore Tso <tytso@mit.edu>
Cc: David Howells <dhowells@redhat.com>,
Christoph Hellwig <hch@infradead.org>,
aviro@redhat.com, akpm@osdl.org, linux-fsdevel@vger.kernel.org
Subject: Re: 64-bit inode number issues
Date: Sun, 8 Oct 2006 12:02:12 -0400 [thread overview]
Message-ID: <20061008160212.GA2383@devserv.devel.redhat.com> (raw)
In-Reply-To: <20061008020035.GE5478@thunk.org>
On Sat, Oct 07, 2006 at 10:00:35PM -0400, Theodore Tso wrote:
> On Wed, Oct 04, 2006 at 03:23:49PM +0100, David Howells wrote:
> > David Howells <dhowells@redhat.com> wrote:
> >
> > > This problem doesn't just apply to NFS. It applies to any filesystem that can
> > > generate 64-bit inode numbers - which includes Ext3, I believe
> >
> > Actually, Ext3 can't do 64-bit inode numbers. I'd misremembered what Stephen
> > told me.
>
> Nope, we've thought about using 64-bit inode numbers for ext4, however
> --- it would solve a number of problems for us. Unfortunately, given
> issues with 64-bit inods at the VFS, glibc, and userspace layers, we
> decided it wasn't worth the pain and suffering that would be
> involved....
VFS is fine with those... glibc probably should be OK; userland might
be nasty, though.
next prev parent reply other threads:[~2006-10-08 16:02 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-28 16:45 fscache review comments, part 1 Christoph Hellwig
2006-09-28 17:30 ` Andreas Dilger
2006-09-29 0:02 ` Christoph Hellwig
2006-09-29 1:51 ` Timothy Shimmin
2006-09-29 8:38 ` David Howells
2006-10-02 13:40 ` David Howells
2006-10-02 17:39 ` Andrew Morton
2006-10-02 21:41 ` Christoph Hellwig
2006-10-04 13:44 ` Al Viro
2006-10-04 14:18 ` 64-bit inode number issues David Howells
2006-10-04 14:23 ` David Howells
2006-10-08 2:00 ` Theodore Tso
2006-10-08 16:02 ` Alexander Viro [this message]
2006-10-07 21:01 ` Christoph Hellwig
2006-10-09 7:58 ` David Howells
2006-10-09 9:01 ` David Chinner
2006-10-09 11:32 ` David Howells
2006-10-09 14:12 ` Arjan van de Ven
2006-10-09 23:53 ` David Chinner
2006-10-12 18:32 ` Benjamin LaHaise
2006-10-17 6:02 ` Chris Wedgwood
2006-10-09 13:46 ` fscache review comments, part 1 David Howells
2006-10-10 13:31 ` Christoph Hellwig
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=20061008160212.GA2383@devserv.devel.redhat.com \
--to=aviro@redhat.com \
--cc=akpm@osdl.org \
--cc=dhowells@redhat.com \
--cc=hch@infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=tytso@mit.edu \
/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.