Re: FS-specified FSID for non-device based filesystems?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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
-
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Ext4 Filesystem]     [Union Filesystem]     [Filesystem Testing]     [Ceph Users]     [Ecryptfs]     [AutoFS]     [Kernel Newbies]     [Share Photos]     [Security]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux Cachefs]     [Reiser Filesystem]     [Linux RAID]     [Samba]     [Device Mapper]     [CEPH Development]
  Powered by Linux