From: UZAIR LAKHANI Subject: Inode Handling in Client/Server Environment Date: Tue, 9 May 2006 05:04:47 -0700 (PDT) Message-ID: <20060509120447.61454.qmail@web37905.mail.mud.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7BIT Return-path: Received: from web37905.mail.mud.yahoo.com ([209.191.124.100]:62356 "HELO web37905.mail.mud.yahoo.com") by vger.kernel.org with SMTP id S932391AbWEIMEs (ORCPT ); Tue, 9 May 2006 08:04:48 -0400 To: linux-fsdevel@vger.kernel.org Sender: linux-fsdevel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org Hello All, Consider a situation of a filesystem having a single server and a single client. Since the actual files and directories are on the server, therefore the actual inodes are present on server but since client will also need inode information in different cases e.g. one may be the case of changing negative dentries into positive. I want to find out if I have to bring each and every inode on server to client machine. If yes then I also need to make room for storing these inodes (meta data) on client side. Additionally I can cache these inodes but again I will get the size problem regarding how many inodes can be cached. Which approach will be best. Actually storing inodes on client or caching these inodes on client side. Thanks, -- Uzair Mehdi Lakhani __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com