xfs
[Top] [All Lists]

Re: stale NFS file handle problem on XFS inode64

To: hank peng <pengxihan@xxxxxxxxx>
Subject: Re: stale NFS file handle problem on XFS inode64
From: Emmanuel Florac <eflorac@xxxxxxxxxxxxxx>
Date: Mon, 21 Nov 2011 16:43:09 +0100
Cc: linux-xfs@xxxxxxxxxxx
In-reply-to: <CAJNJY8QciPX_MPsgPo3SfSuheFHGSZVsiL=ibNf1S3spyKFAig@xxxxxxxxxxxxxx>
Organization: Intellique
References: <CAJNJY8Q--O2Z3K6KFxVKOivwaABk+oRtC1y0eQ0nS1WdPNMwsQ@xxxxxxxxxxxxxx> <20111121150158.5f8b2512@xxxxxxxxxxxxxxxxxxxx> <CAJNJY8SoNvqQB0WNJq5SVUhkLSJROoMkVEkOHrESVR0iMB4JDA@xxxxxxxxxxxxxx> <20111121162155.0bfa0342@xxxxxxxxxxxxxxxxxxxx> <CAJNJY8QciPX_MPsgPo3SfSuheFHGSZVsiL=ibNf1S3spyKFAig@xxxxxxxxxxxxxx>
Le Mon, 21 Nov 2011 23:28:23 +0800
hank peng <pengxihan@xxxxxxxxx> é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@xxxxxxxxxxxxxx>
                    |   +33 1 78 94 84 02
------------------------------------------------------------------------

<Prev in Thread] Current Thread [Next in Thread>