From: "J. Bruce Fields" <bfields@fieldses.org>
To: Christoph Hellwig <hch@infradead.org>
Cc: Michael Monnerie <michael.monnerie@is.it-management.at>,
linux-nfs@vger.kernel.org
Subject: Re: XFS, NFS and inode64 on 2.6.27
Date: Wed, 25 Nov 2009 18:55:44 -0500 [thread overview]
Message-ID: <20091125235543.GA4928@fieldses.org> (raw)
In-Reply-To: <20091125211324.GA12833@infradead.org>
On Wed, Nov 25, 2009 at 04:13:24PM -0500, Christoph Hellwig wrote:
> On Mon, Nov 23, 2009 at 10:51:09AM -0500, J. Bruce Fields wrote:
> > But not the other four directories? What error do you get when you try?
> > What client are you using, and are you mounting with NFSv2, NFSv3, or
> > NFSv4? Could we see a network trace of a failed mount? (So, run
>
> >From information Michael posted on the xfs list he is not exporting the
> root of filesystems, which means we use a file system handle format that
> needs to encode the inode. And all but the uuid16 format can only
> encode 32 bit inode numbers. I very strongly suspect that this is the
> underlying issue here, but I'm currenly not uptodate on the filesystem
> handle selection in nfsutils.
If using an nfs-utils recent enough to pass down a uuid (can check this
by looking at /proc/net/rpc/nfsd.export/filehandle after trying to
access those directories, and seeing whether there's a uuid= option
set), then I'd expect it to be using FSID_UUID16_INUM with v3 or v4 (v2
doesn't have large enough filehandles).
--b.
next prev parent reply other threads:[~2009-11-25 23:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-23 13:19 XFS, NFS and inode64 on 2.6.27 Michael Monnerie
[not found] ` <200911231419.50678-xqLQU7OFoCs@public.gmane.org>
2009-11-23 15:51 ` J. Bruce Fields
2009-11-25 21:13 ` Christoph Hellwig
2009-11-25 23:55 ` J. Bruce Fields [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-11-20 10:52 Michael Monnerie
2009-11-20 21:23 ` Nathaniel W. Turner
2009-11-21 10:47 ` Michael Monnerie
2009-11-21 13:16 ` Christoph Hellwig
2009-11-21 21:17 ` Michael Monnerie
2009-11-22 12: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=20091125235543.GA4928@fieldses.org \
--to=bfields@fieldses.org \
--cc=hch@infradead.org \
--cc=linux-nfs@vger.kernel.org \
--cc=michael.monnerie@is.it-management.at \
/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.