Gluster users - May 2017 - Hash function

Hi all,

Am I correct in thinking the has used to determine the storage brick used
only looks at the file name (not the path)?

If so can this functionality be overridden to potentially only use the
path? My volume contains lots of files however only about 12 different
filenames! Processing is also done on a per directory basis.

Any advice would be appreciated.

Steve
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.gluster.org/pipermail/gluster-users/attachments/20170528/aef6797b/attachment.html>

Hashing is done on filenames, but each directory has its own hash
range. So same filename under different directories mapped to
different bricks.

On Sun, May 28, 2017 at 1:00 PM, Stephen Remde
<stephen.remde at gaist.co.uk> wrote:
> Hi all,
>
> Am I correct in thinking the has used to determine the storage brick used
> only looks at the file name (not the path)?
>
> If so can this functionality be overridden to potentially only use the
path?
> My volume contains lots of files however only about 12 different filenames!
> Processing is also done on a per directory basis.
>
> Any advice would be appreciated.
>
> Steve
>
> _______________________________________________
> Gluster-users mailing list
> Gluster-users at gluster.org
> http://lists.gluster.org/mailman/listinfo/gluster-users