From mboxrd@z Thu Jan 1 00:00:00 1970 From: Trond Myklebust Subject: Re: [nfsv4] RE: Finding hardlinks Date: Fri, 05 Jan 2007 17:56:24 +0100 Message-ID: <1168016184.6050.71.camel@lade.trondhjem.org> References: <4593C524.8070209@poochiereds.net> <4593DEF8.5020609@panasas.com> <1167388129.6106.45.camel@lade.trondhjem.org> <1167780097.6090.104.camel@lade.trondhjem.org> <459BA30A.4020809@panasas.com> <1167899796.6046.11.camel@lade.trondhjem.org> <459CD11E.3000200@panasas.com> <20070105164008.GA1010@binky.Central.Sun.COM> Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Cc: Benny Halevy , Jan Harkes , Miklos Szeredi , nfsv4@ietf.org, linux-kernel@vger.kernel.org, Mikulas Patocka , linux-fsdevel@vger.kernel.org, Jeff Layton , Arjan van de Ven Return-path: Received: from pat.uio.no ([129.240.10.15]:40856 "EHLO pat.uio.no" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1161152AbXAEQ4x (ORCPT ); Fri, 5 Jan 2007 11:56:53 -0500 To: Nicolas Williams In-Reply-To: <20070105164008.GA1010@binky.Central.Sun.COM> Sender: linux-fsdevel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org On Fri, 2007-01-05 at 10:40 -0600, Nicolas Williams wrote: > What I don't understand is why getting the fileid is so hard -- always > GETATTR when you GETFH and you'll be fine. I'm guessing that's not as > difficult as it is to maintain a hash table of fileids. You've been sleeping in class. We always try to get the fileid together with the GETFH. The irritating bit is having to redo a GETATTR using the old filehandle in order to figure out if the 2 filehandles refer to the same file. Unlike filehandles, fileids can be reused. Then there is the point of dealing with that servers can (and do!) actually lie to you. Trond