On Wed, Feb 13, 2013 at 10:14:55AM -0500, Theodore Ts'o wrote: > On Wed, Feb 13, 2013 at 08:31:31AM -0500, J. Bruce Fields wrote: > > They're assuming they can take the high bits of the cookie for their own > > use. > > > > (In more detail: they're spreading a single directory across multiple > > nodes, and encoding a node ID into the cookie they return, so they can > > tell which node the cookie came from when they get it back.) > > > > That works if you assume the cookie is an "offset" bounded above by some > > measure of the directory size, hence unlikely to ever use the high > > bits.... > > Right, but why wouldn't a nfs export option solave the problem for > gluster? No, gluster is running on ext4 directly. > Basically, it would be nice if we did not have to degrade locally > running userspace applications by globally turning off 64-bit telldir > cookies just because there are some broken cluster file systems and > nfsv3 clients out there. And if we are only turning off 64-bit > cookies for NFS, wouldn't it make sense to make this be a NFS export > option, as opposed to a mount option? Right, the problem is that from ext4's point of view gluster is just another userspace application. (And my worry of course is that there may be others. Samba would be another one to check.) --b. -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
