From: Dave Chinner <david@fromorbit.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Samuel Kvasnica <samuel.kvasnica@ims.co.at>, xfs@oss.sgi.com
Subject: Re: [PATCH] xfs: fix exporting with left over 64-bit inodes
Date: Mon, 22 Nov 2010 11:37:54 +1100 [thread overview]
Message-ID: <20101122003754.GE13830@dastard> (raw)
In-Reply-To: <20101119133848.GA5471@infradead.org>
On Fri, Nov 19, 2010 at 08:38:49AM -0500, Christoph Hellwig wrote:
> From: Samuel Kvasnica <samuel.kvasnica@ims.co.at>
>
> We now support mounting and using filesystems with 64-bit inodes even
> when not mounted with the inode64 option (which now only controls if
> we allocate new inodes in that space or not). Make sure we always
> use large NFS file handles when exporting a filesystem that may contain
> 64-bit inodes. Note that this only affects newly generated file handles,
> any outstanding 32-bit file handle is still accepted.
>
> [hch: the comment and commit log are mine, the rest is from a patch
> snipplet from Samuel]
>
> Signed-off-by: Christoph Hellwig <hch@lst.de>
Won't this mean that people exporting non-root directories suddenly
have those exports stop working on a kernel upgrade due to changing
the handle format?
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2010-11-22 0:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-19 13:38 [PATCH] xfs: fix exporting with left over 64-bit inodes Christoph Hellwig
2010-11-20 8:29 ` Michael Monnerie
2010-11-21 10:57 ` Christoph Hellwig
2010-11-22 0:37 ` Dave Chinner [this message]
2010-11-22 9:05 ` Samuel Kvasnica
2010-11-22 10:23 ` 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=20101122003754.GE13830@dastard \
--to=david@fromorbit.com \
--cc=hch@infradead.org \
--cc=samuel.kvasnica@ims.co.at \
--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 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.