On Thu, Jun 24, 2010 at 05:06:45PM -0600, Andreas Dilger wrote: > I think the right solution for this issue is to (gradually) start enforcing the "uniqueness" of the UUID in the filesystem superblock. That is what it is supposed to be for. Using (fsid, st_inode) doesn't necessarily help anything, if "fsid" isn't unique, and the same "st_inode" number is used on two different mountpoints. > > To start, tracking the UUID at mount time an printing a non-fatal error at mount time if the mounted UUID is not unique would help, as would having e.g. fsck track the UUIDs of the underlying filesystems and printing a non-fatal error if it hits a duplicate UUID. > > At some point in the future, the kernel can be changed to refuse to mount a filesystem with a duplicate UUID. I believe mount.xfs already does this. Tracking and exposing the uuid to be exact. Having the full uuid in a statfs/statvfs-like system call is one first step. And yes, XFS does check the uuid during mount. But it's actually in kernelspace, not in a mount helper which XFS doesn't have. Take a look at xfs_uuid_mount(). -- 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
