From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from cuda.sgi.com (cuda3.sgi.com [192.48.176.15]) by oss.sgi.com (8.14.3/8.14.3/SuSE Linux 0.8) with ESMTP id q0OHwTko060219 for ; Tue, 24 Jan 2012 11:58:29 -0600 Received: from bombadil.infradead.org (173-166-109-252-newengland.hfc.comcastbusiness.net [173.166.109.252]) by cuda.sgi.com with ESMTP id VQajdH3YfENOJUP5 (version=TLSv1 cipher=AES256-SHA bits=256 verify=NO) for ; Tue, 24 Jan 2012 09:58:29 -0800 (PST) Date: Tue, 24 Jan 2012 12:58:26 -0500 From: Christoph Hellwig Subject: Re: xfs: validate inode numbers in file handles correctly--NFS Stale File Handle Again Message-ID: <20120124175826.GA23671@infradead.org> References: <1276846374-23916-1-git-send-email-david@fromorbit.com> <20111123143045.GA20892@infradead.org> <20111128111947.GA26454@infradead.org> <20120102150201.GB31110@infradead.org> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: List-Id: XFS Filesystem from SGI List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xfs-bounces@oss.sgi.com Errors-To: xfs-bounces@oss.sgi.com To: yangguoquan Cc: hch@infradead.org, linux-xfs@oss.sgi.com, pengxihan@gmail.com On Wed, Jan 04, 2012 at 10:20:31AM +0800, yangguoquan wrote: > > Yes, They are mount points. > > /dev/mapper/storage_pool-testnfs00 on /mnt/storage_pool/testnfs00 type xfs (rw) In that case I really have no idea. Did you make sure you no outstanding "old" filehandles before the fix on clients? How do the handles look in wireshark traces? _______________________________________________ xfs mailing list xfs@oss.sgi.com http://oss.sgi.com/mailman/listinfo/xfs