From mboxrd@z Thu Jan 1 00:00:00 1970 From: "J. Bruce Fields" Subject: Re: FS-specified FSID for non-device based filesystems? Date: Fri, 14 Apr 2006 16:59:48 -0400 Message-ID: <20060414205948.GG30419@fieldses.org> References: <20060412111003.GZ26989@linuxhacker.ru> <20060414204543.GE10907@linuxhacker.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Bryan Henderson , linux-fsdevel@vger.kernel.org, neilb@cse.unsw.edu.au Return-path: Received: from mail.fieldses.org ([66.93.2.214]:27331 "EHLO pickle.fieldses.org") by vger.kernel.org with ESMTP id S965155AbWDNU7z (ORCPT ); Fri, 14 Apr 2006 16:59:55 -0400 To: Oleg Drokin Content-Disposition: inline In-Reply-To: <20060414204543.GE10907@linuxhacker.ru> Sender: linux-fsdevel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org On Fri, Apr 14, 2006 at 11:45:43PM +0300, Oleg Drokin wrote: > 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. Wouldn't some ways of identifying filesystems (ext2/3 labels?) more easily be done from userspace? Would it be possible to do what you want from userspace using the fsid export option? There's no reason the fsid= option has to be set manually; you could generate /etc/exports lines (or exportfs commands) automatically. --b.