All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: "J. Bruce Fields" <bfields@fieldses.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 16:13:24 -0500	[thread overview]
Message-ID: <20091125211324.GA12833@infradead.org> (raw)
In-Reply-To: <20091123155109.GA3292@fieldses.org>

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.


  reply	other threads:[~2009-11-25 21:13 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 [this message]
2009-11-25 23:55       ` J. Bruce Fields
  -- 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=20091125211324.GA12833@infradead.org \
    --to=hch@infradead.org \
    --cc=bfields@fieldses.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.