From: Trond Myklebust Subject: Re: inconsistent mount attributes (ro/rw), RHEL5 / Netapp Date: Sat, 05 May 2007 14:49:20 -0400 Message-ID: <1178390960.6561.61.camel@heimdal.trondhjem.org> References: <46269362.5040608@amd.com> <1176948355.6422.72.camel@heimdal.trondhjem.org> <4627B3DD.5050409@amd.com> <1177007479.6623.14.camel@heimdal.trondhjem.org> <4627D303.8060009@amd.com> <1177020662.6628.30.camel@heimdal.trondhjem.org> <4627EBFC.2090704@amd.com> <462CFC92.2080201@amd.com> <463B97E6.4030009@amd.com> <1178314889.6533.19.camel@heimdal.trondhjem.org> <1178379473.4559.24.camel@raven.themaw.net> <1178385472.6561.43.camel@heimdal.trondhjem.org> <1178389675.4559.29.camel@raven.themaw.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Cc: Paul Krizak , nfs@lists.sourceforge.net To: Ian Kent Return-path: Received: from sc8-sf-mx1-b.sourceforge.net ([10.3.1.91] helo=mail.sourceforge.net) by sc8-sf-list2-new.sourceforge.net with esmtp (Exim 4.43) id 1HkPJv-00050l-EB for nfs@lists.sourceforge.net; Sat, 05 May 2007 11:49:31 -0700 Received: from mx2.netapp.com ([216.240.18.37]) by mail.sourceforge.net with esmtp (Exim 4.44) id 1HkPJy-0002Xx-2h for nfs@lists.sourceforge.net; Sat, 05 May 2007 11:49:30 -0700 In-Reply-To: <1178389675.4559.29.camel@raven.themaw.net> List-Id: "Discussion of NFS under Linux development, interoperability, and testing." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: nfs-bounces@lists.sourceforge.net Errors-To: nfs-bounces@lists.sourceforge.net On Sun, 2007-05-06 at 02:27 +0800, Ian Kent wrote: > On Sat, 2007-05-05 at 13:17 -0400, Trond Myklebust wrote: > > Why are people arguing that NFS should be working in a completely > > different fashion to all other filesystems? Fix the VFS to allow > > read-only bind mounts, and NFS will work just fine with that. > > Sorry, I don't follow. > How does think affect a client doing two distinct mounts to a server. > Are you suggesting that such a bind mount should be done on the server > and then exported? I guess that would give us distinct super blocks. No. People are arguing that the client should allow the _same_ filesystem to be mounted both read-only and read-write. That is not currently permitted for any other filesystem. The reason is that the read-only flag acts on a per-superblock basis, and hence on a per-filesystem basis. This is why you cannot do mount --bind -oro /foo /bar If you fix the VFS to allow the above by making the read-only flag a per-mountpoint flag instead of a per-superblock flag, then NFS can happily do the same. Trond ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ NFS maillist - NFS@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nfs