From: Christoph Hellwig <hch@infradead.org>
To: David Howells <dhowells@redhat.com>
Cc: Christoph Hellwig <hch@infradead.org>,
aviro@redhat.com, akpm@osdl.org, linux-fsdevel@vger.kernel.org
Subject: Re: 64-bit inode number issues
Date: Sat, 7 Oct 2006 22:01:32 +0100 [thread overview]
Message-ID: <20061007210131.GA17717@infradead.org> (raw)
In-Reply-To: <13246.1159971501@warthog.cambridge.redhat.com>
On Wed, Oct 04, 2006 at 03:18:21PM +0100, David Howells wrote:
> > Unfortunately there's a lot of broken userspace that can't deal
> > with 64bit inode numbers, so you need to make the lod behaviour
> > a mount option at least, probably even the default. Given that
> > we're going to run into problems like that it might make sense
> > to make the option VFS-level instead of just in nfs. (Note:
> > XFS already has an option like that)
>
> 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 - so not
> applying the NFS patch doesn't really solve your problem (Al Viro asked me for
> examples of that, btw) and leaves my problem unsolved.
As you mention in your next mail ext3 is not affected. XFS for example
is, that's why it has a 32bit inode numbers only mount option already.
> I think any solution has to apply at the VFS level or higher. I'm not sure Al
> agrees though. I think we have to do one of the following:
>
> (1) Turn on inode number compression (which tries to hide the problem).
>
> (2) Give an error to stat and getdents if the inode number can't be
> represented by 32-bits.
>
> And I think we're going to do this, that we need to do this on a per-superblock
> basis or on a per-system basis, and I think it should be _off_ by default. It
> might also be possible to do it on a per-process level, but I suspect that'd be
> too much effort.
This definitly should be on a per-superblock basis, aka the mount option
I suggested above. I don't think an actual scheme to deal with the
inode numbers at the VFS level makes sense, what I meant was only to do
a vfs-level mount option (numerical) instead of a per-filesystem one.
Al commented he doesn't like that. He also think we should give the
64bit inode numbers a try, so I'd say:
o add an inode32 option for nfs that mirrors the XFS option
o turn it off by default in -mm and see what goes boom
next prev parent reply other threads:[~2006-10-07 21:01 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
2006-10-07 21:01 ` Christoph Hellwig [this message]
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=20061007210131.GA17717@infradead.org \
--to=hch@infradead.org \
--cc=akpm@osdl.org \
--cc=aviro@redhat.com \
--cc=dhowells@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
/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.