All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Christoph Hellwig <hch@infradead.org>,
	dhowells@redhat.com, akpm@osdl.org,
	linux-fsdevel@vger.kernel.org
Subject: Re: fscache review comments, part 1
Date: Fri, 29 Sep 2006 01:02:07 +0100	[thread overview]
Message-ID: <20060929000207.GA22100@infradead.org> (raw)
In-Reply-To: <20060928173017.GE22010@schatzie.adilger.int>

On Thu, Sep 28, 2006 at 11:30:17AM -0600, Andreas Dilger wrote:
> On Sep 28, 2006  17:45 +0100, Christoph Hellwig wrote:
> > 02-ino64-nfs.diff:
> > 	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)
> 
> A general question - is there a known list of common applications that have
> problems with 64-bit inodes?  It's been mentioned several times, but I'm
> wondering if any effort is going toward fixing those apps so that 5 years
> from now (or whenever) we CAN have 64-bit inodes.  If it relates to on-disk
> formats like ustar, we can always work with something like star to ensure
> that it is useful in the future.

The most important ones we've seen at SGI were various version of tar
and many commercial backup applications that silently (!) lost data
on restore with 64bit inode numbers.  I wasn't directly involved with
those issue, but maybe some people that were at SGI at that time can
fill in more details.

  reply	other threads:[~2006-09-29  0: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 [this message]
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
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=20060929000207.GA22100@infradead.org \
    --to=hch@infradead.org \
    --cc=akpm@osdl.org \
    --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.