From: Trond Myklebust Subject: Re: nfs exporting my stacked fs Date: Sat, 31 May 2003 04:44:56 +0200 Sender: linux-fsdevel-owner@vger.kernel.org Message-ID: <16088.5928.60451.265526@charged.uio.no> References: Reply-To: trond.myklebust@fys.uio.no Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: Andrew Sharp , linux-fsdevel@vger.kernel.org Return-path: Received: from pat.uio.no ([129.240.130.16]:38390 "EHLO pat.uio.no") by vger.kernel.org with ESMTP id S264108AbTEaCb4 (ORCPT ); Fri, 30 May 2003 22:31:56 -0400 To: Bryan Henderson In-Reply-To: List-Id: linux-fsdevel.vger.kernel.org >>>>> " " == Bryan Henderson writes: > In a typical NFS 2/3 implementation, a device number fills the > role of fsid. I think we can agree that absent some > simplifying assumptions, that means two equal file handles from > a server could refer to two different files. Then server admins are deliberately putting themselves in a situation where their users may see data corruption. The above problem is trivially solved by means of the 'fsid' export option. For most setups, this should not be necessary (since device numbers will suffice). Those that don't have permanently allocated device numbers (e.g. fibre channel), should use the fsid export option in order to provide a permanent value... > I think we're all still looking for a practical implementation > that approaches the ideals of the RFC. I hope not. Cheers, Trond