So in a distributed cluster, the GFID tells all bricks what a files preceding directory structure looks like? Where the physical file is saved is a function of the filename ONLY. Therefore My requirement should be met by default, or am I being dense? BR Jan On 2014/11/25, 8:15 PM, "Shyam" <srangana@xxxxxxxxxx> wrote: >On 11/25/2014 03:11 PM, Jan H Holtzhausen wrote: >> STILL doesn’t work … exact same file ends up on 2 different bricks … >> I must be missing something. >> All I need is for: >> /directory1/subdirectory2/foo >> And >> /directory2/subdirectoryaaa999/foo >> >> >> To end up on the same brick…. > >This is not possible is what I was attempting to state in the previous >mail. The regex filter is not for this purpose. > >The hash is always based on the name of the file, but the location is >based on the distribution/layout of the directory, which is different >for each directory based on its GFID. > >So there are no options in the code to enable what you seek at present. > >Why is this needed? > >Shyam _______________________________________________ Gluster-devel mailing list Gluster-devel@xxxxxxxxxxx http://supercolony.gluster.org/mailman/listinfo/gluster-devel
