From: Emmanuel Florac <eflorac@intellique.com>
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 16:43:09 +0100 [thread overview]
Message-ID: <20111121164309.4b18a6ca@harpe.intellique.com> (raw)
In-Reply-To: <CAJNJY8QciPX_MPsgPo3SfSuheFHGSZVsiL=ibNf1S3spyKFAig@mail.gmail.com>
Le Mon, 21 Nov 2011 23:28:23 +0800
hank peng <pengxihan@gmail.com> écrivait:
> I noticed that there is a kernel parameter :
> nfs.enable_ino64=
> [NFS] enable 64-bit inode numbers.
> If zero, the NFS client will fake up a 32-bit
> inode number for the readdir() and stat() syscalls instead
> of returning the full 64-bit number.
> The default is to return 64-bit inode numbers.
>
> can I set it to zero, so NFS client can get converted 32bit inode ?
Well you must try it and hope for the best!
--
------------------------------------------------------------------------
Emmanuel Florac | Direction technique
| Intellique
| <eflorac@intellique.com>
| +33 1 78 94 84 02
------------------------------------------------------------------------
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2011-11-21 15:43 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 [this message]
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
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=20111121164309.4b18a6ca@harpe.intellique.com \
--to=eflorac@intellique.com \
--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