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, 28 Nov 2011 06:09:41 -0500 [thread overview]
Message-ID: <20111128110941.GE13766@infradead.org> (raw)
In-Reply-To: <CAJNJY8Q3u6zZYHVdxnka160f+EC21JxoBe4EyKk=vDQgH4T19w@mail.gmail.com>
On Wed, Nov 23, 2011 at 09:19:26AM +0800, hank peng wrote:
> yes, I have already done that. I mount the expoted NFS directory in
> same machine(kernel version is 2.6.35.6), but it still didn't work.
Ok, sounds like this is a server side issue.
>
> Then, I used fsid=$(my exported filesystem ID) option in /etc/exports
> and tried again, it still gave me back "stale NFS file handle" when
> entering a specific subdirectory.
> I noticed that from NFS client(in same machine with NFS server) side,
> the inode number of this subdirectory was changed to be within 32
> limit, but still "stale NFS file handle" came back.
Do you mean the NFS mount displayed a 32-bit inode number, but it was still
64-bit on the XFS filesystem directly? Can you post the inode numbers
(e.g. from ls -i) for both sides?
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2011-11-28 11:09 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
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 [this message]
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=20111128110941.GE13766@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