Re: stale NFS file handle problem on XFS inode64

[hank peng <pengxihan@xxxxxxxxx>]

2011/11/21 Emmanuel Florac <eflorac@xxxxxxxxxxxxxx>:
> Le Mon, 21 Nov 2011 23:02:32 +0800
> hank peng <pengxihan@xxxxxxxxx> écrivait:
>
>> no, client and server are both 32 bits kernel.
>>
>
> I'm afraid the 32 bits nfs client can't manage 64 bits inodes at all.
> Maybe with a much more recent kernel, something like 2.6.29 or better?
>

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 ?

> See for instance
> http://oss.sgi.com/archives/xfs/2009-11/msg00174.html
>
> Your best choice is to revert to not using the "inode64" option.
> Unfortunately the easiest way is to backup and restore the whole
> filesystem.
>
> Alternatively, switch to samba...
>
> --
> ------------------------------------------------------------------------
> Emmanuel Florac     |   Direction technique
>                    |   Intellique
>                    |   <eflorac@xxxxxxxxxxxxxx>
>                    |   +33 1 78 94 84 02
> ------------------------------------------------------------------------
>



-- 
The simplest is not all best but the best is surely the simplest!