From: Christoph Hellwig <hch@infradead.org>
To: hank peng <pengxihan@gmail.com>
Cc: linux-xfs@oss.sgi.com
Subject: Re: stale NFS file handle problem on XFS inode64
Date: Mon, 21 Nov 2011 12:04:59 -0500 [thread overview]
Message-ID: <20111121170459.GA1327@infradead.org> (raw)
In-Reply-To: <CAJNJY8Q--O2Z3K6KFxVKOivwaABk+oRtC1y0eQ0nS1WdPNMwsQ@mail.gmail.com>
On Mon, Nov 21, 2011 at 09:00:57PM +0800, hank peng wrote:
> Hi:
> I have a 4TB XFS filesystem mounted with "inode64" option, and I
> exported it using NFS v3, on NFS client, I entered a subdirectory and
> got "stale NFS file handle" error.
> ls -il showed that its inode number exceed 32 bit limit.
> NFS server: kernel version is 2.6.35.6
> NFS client: kernel version is 2.6.18
Do you export the root directory of the XFS filesystem, or a
subdirectory in it? If it's the former it should work in theory,
althrough I'm not sure how well 64-bit inode numbers work with a client
that old, if it's the latter it needs a few tweaks to work, see
http://xfs.org/index.php/XFS_FAQ#Q:_Why_doesn.27t_NFS-exporting_subdirectories_of_inode64-mounted_filesystem_work.3F
for details.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2011-11-21 17:05 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-21 13:00 stale NFS file handle problem on XFS inode64 hank peng
2011-11-21 14:01 ` Emmanuel Florac
2011-11-21 15:02 ` hank peng
2011-11-21 15:21 ` Emmanuel Florac
2011-11-21 15:28 ` hank peng
2011-11-21 15:43 ` Emmanuel Florac
2011-11-22 7:14 ` hank peng
2011-11-21 17:04 ` Christoph Hellwig [this message]
2011-11-22 0:19 ` hank peng
2011-11-22 1:46 ` Dave Chinner
2011-11-22 3:22 ` hank peng
2011-11-22 20:35 ` Emmanuel Florac
2011-11-22 22:16 ` Christoph Hellwig
2011-11-22 22:15 ` Christoph Hellwig
2011-11-23 1:19 ` hank peng
2011-11-28 11:09 ` 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=20111121170459.GA1327@infradead.org \
--to=hch@infradead.org \
--cc=linux-xfs@oss.sgi.com \
--cc=pengxihan@gmail.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