From: Dave Chinner <david@fromorbit.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: xfs@oss.sgi.com
Subject: Re: [PATCH 2/2] allow inode64 mount option on 32 bit systems
Date: Tue, 28 Oct 2008 10:37:21 +1100 [thread overview]
Message-ID: <20081027233721.GI4985@disturbed> (raw)
In-Reply-To: <20081027133015.GC30607@infradead.org>
On Mon, Oct 27, 2008 at 09:30:15AM -0400, Christoph Hellwig wrote:
> Now that we've stopped using the Linux inode cache when can trivally
> support the inode64 mount option on 32bit architectures. As far as the
> kernel and most userspace is concerned this works perfectly, but
> applications still using really old stat and readdir interfaces will get
> an EOVERFLOW error when hitting an inode number not fitting into 32
> bits (that problem of course also exists when using these applications
> on a 64bit kernel).
>
> Note that because inode64 is simply a mount option we can currently
> mount a filesystem having > 32 bit inode numbers and cause a variety of
> problems, all this is solved but this patch which enables XFS_BIG_INUMS,
> even when inode64 is not used.
>
> (First sent on October 18th)
>
>
> Signed-off-by: Christoph Hellwig <hch@lst.de>
Reviewed-by; Dave Chinner <david@fromorbit.com>
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2008-10-27 23:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-27 13:30 [PATCH 2/2] allow inode64 mount option on 32 bit systems Christoph Hellwig
2008-10-27 23:37 ` Dave Chinner [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-10-26 20:34 Christoph Hellwig
2008-10-27 1:21 ` Dave Chinner
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=20081027233721.GI4985@disturbed \
--to=david@fromorbit.com \
--cc=hch@infradead.org \
--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