From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from cuda.sgi.com (cuda1.sgi.com [192.48.157.11]) by oss.sgi.com (8.14.3/8.14.3/SuSE Linux 0.8) with ESMTP id pALFM1iJ006175 for ; Mon, 21 Nov 2011 09:22:02 -0600 Received: from smtp4-g21.free.fr (localhost [127.0.0.1]) by cuda.sgi.com (Spam Firewall) with ESMTP id F13AD1629C08 for ; Mon, 21 Nov 2011 07:21:58 -0800 (PST) Received: from smtp4-g21.free.fr (smtp4-g21.free.fr [212.27.42.4]) by cuda.sgi.com with ESMTP id Xf0vzg3nSoOVFoUE for ; Mon, 21 Nov 2011 07:21:58 -0800 (PST) Date: Mon, 21 Nov 2011 16:21:55 +0100 From: Emmanuel Florac Subject: Re: stale NFS file handle problem on XFS inode64 Message-ID: <20111121162155.0bfa0342@harpe.intellique.com> In-Reply-To: References: <20111121150158.5f8b2512@harpe.intellique.com> Mime-Version: 1.0 List-Id: XFS Filesystem from SGI List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Sender: xfs-bounces@oss.sgi.com Errors-To: xfs-bounces@oss.sgi.com To: hank peng Cc: linux-xfs@oss.sgi.com Le Mon, 21 Nov 2011 23:02:32 +0800 hank peng =E9crivait: > 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? = 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 | | +33 1 78 94 84 02 ------------------------------------------------------------------------ _______________________________________________ xfs mailing list xfs@oss.sgi.com http://oss.sgi.com/mailman/listinfo/xfs