On 2010-02-26, at 12:21, J. Bruce Fields wrote:
On Sun, Feb 21, 2010 at 11:42:45AM -0700, Andreas Dilger wrote:
Yes, we looked at this in the past for Lustre as well, and while we
had
proposed a patch for the NFSd code to extract the FSID from the
filesystem, it was turned down because "setting the FSID via a
userspace
file is the right thing to do". I have enough on my plate not to
wage an
uphill battle for this.
I agree that a cluster filesystem shouldn't need fsid= set right
across
all servers.
But doesn't the libblkid uuid stuff as it's now implemented give you
what you need?
I'm not sure what you mean? On the clients (where the NFS servers are
running) there are no block devices, so I don't think libblkid is
relevant. Lustre itself already can provide a UUID/fsid that is the
same on all clients, but there is no way to pass this to NFSd.
If there is interest to revive this idea, I'll try to dig up the old
patches we had. I believe that they set a FS_NFS_FSID (or similarly
named) flag in the file_system_type, and possibly a method that
extracted this information for NFSd.
Cheers, Andreas
--
Andreas Dilger
Sr. Staff Engineer, Lustre Group
Sun Microsystems of Canada, Inc.
--
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
