From: Christoph Hellwig <hch@infradead.org>
To: Michael Monnerie <michael.monnerie@is.it-management.at>
Cc: Christoph Hellwig <hch@infradead.org>,
Samuel Kvasnica <samuel.kvasnica@ims.co.at>,
xfs@oss.sgi.com
Subject: Re: [PATCH] xfs: fix exporting with left over 64-bit inodes
Date: Sun, 21 Nov 2010 05:57:03 -0500 [thread overview]
Message-ID: <20101121105703.GA24432@infradead.org> (raw)
In-Reply-To: <201011200929.08113@zmi.at>
On Sat, Nov 20, 2010 at 09:29:06AM +0100, Michael Monnerie wrote:
> On Freitag, 19. November 2010 Christoph Hellwig wrote:
> > 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.
>
> Could that help with the problem of not being able to mount an NFS share
> when the top shared dir itself is a 64bit inode?
No, that's an NFSD issue, and not fixable in XFS itself.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2010-11-21 10:55 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 [this message]
2010-11-22 0:37 ` Dave Chinner
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=20101121105703.GA24432@infradead.org \
--to=hch@infradead.org \
--cc=michael.monnerie@is.it-management.at \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox