From mboxrd@z Thu Jan 1 00:00:00 1970 From: Oleg Drokin Subject: Re: FS-specified FSID for non-device based filesystems? Date: Fri, 14 Apr 2006 23:45:43 +0300 Message-ID: <20060414204543.GE10907@linuxhacker.ru> References: <20060412111003.GZ26989@linuxhacker.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: linux-fsdevel@vger.kernel.org, neilb@cse.unsw.edu.au Return-path: Received: from linuxhacker.ru ([217.76.32.60]:45190 "EHLO shrek.linuxhacker.ru") by vger.kernel.org with ESMTP id S965152AbWDNUqQ (ORCPT ); Fri, 14 Apr 2006 16:46:16 -0400 To: Bryan Henderson Content-Disposition: inline In-Reply-To: Sender: linux-fsdevel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org Hello! On Fri, Apr 14, 2006 at 01:22:14PM -0700, Bryan Henderson wrote: > When Linux added the export ID, at a time when other operating systems > were addressing the problem with the kind of fsid you're proposing, I > believe the point was that in Linux you can have multiple incompatible > exports of the same filesystem -- to give a client the right data, you'd > need to know from which export, not just which filesystem, a given > filehandle came. Well, I do not see how there is a difference. >>From my reading of the code it seems that fsid is composed of device's minor/major and export point's inode ino. I propose to replace (if supported by fs) device's minor/major by some unique number returned by fs itself. Should be no worse than what we have now. Bye, Oleg