Re: [lustre-discuss] GID only mapping in 2.8.60?

> On Nov 4, 2016, at 11:05 PM, Dilger, Andreas wrote: > > Actually, the nodemap feature will work with any client, since it is only > affecting lookups on the MDS and quota on the OSS. Great! :-) > > It probably would take less time for you to implement the flag

Re: [lustre-discuss] GID only mapping in 2.8.60?

Actually, the nodemap feature will work with any client, since it is only affecting lookups on the MDS and quota on the OSS. It probably would take less time for you to implement the flag feature than the time it is taking to create the thousands of UID entries. While I think it should scale

Re: [lustre-discuss] GID only mapping in 2.8.60?

On Nov 4, 2016, at 16:53, Stephane Thiell wrote: > > Hi all, > > I am currently evaluating Lustre 2.8.60 with UID/GID mapping for a Lustre > storage system that will be connected to multiple clusters. These clusters > have matching UIDs but same groups have different

[lustre-discuss] GID only mapping in 2.8.60?

Hi all, I am currently evaluating Lustre 2.8.60 with UID/GID mapping for a Lustre storage system that will be connected to multiple clusters. These clusters have matching UIDs but same groups have different GIDs. Actually GID mapping is working fine but I can’t find an easy way to avoid