Description of problem:
When mounting a volume using 'mount' command, it is possible to pass xlator options using '-oxlator-option=key=value'.
In my case I need to pass two options to a xlator (created by me).
Adding two xlator-options do not does the trick: both
'-oxlator-option=key1=val1 -oxlator-option=key2=val2' or '-oxlator-option=key1=val1,xlator-option=key2=val2' lead to only last value to be transmited to 'glusterfs' command.
Version-Release number of selected component (if applicable):
I'm using 3.13.2 compiled from sources.
Steps to Reproduce:
1. mount -t glusterfs -oxlator-option=key1=val1 -oxlator-option=key2=val2 /path/to/volfile /path/to/mountpoint
Executed command is:
/usr/local/sbin/glusterfs --xlator-option=key2=val2 --process-name fuse --volfile=/path/to/volfile /path/to/mountpoint
Executed command should be:
/usr/local/sbin/glusterfs --xlator-option=key1=val1 --xlator-option=key2=val2 --process-name fuse --volfile=/path/to/volfile /path/to/mountpoint
I patched /sbin/mount.glusterfs to handle one or two values for 'xlator_option' (by just setting xlator_option2 if xlator_option is still set), and it works as expected in this case.
Script 'mount.glusterfs' should be corrected to handle an arbitrary number of values for xlator_option (and this may also applies to other potentialy-multi-valued options).
Created attachment 1433663 [details]
Handle multiples xlator-options
Added a very simple patch against mount.glusterfs to handle multiple 'xlator-option' values.
This bug reported is against a version of Gluster that is no longer maintained (or has been EOL'd). See https://www.gluster.org/release-schedule/ for the versions currently maintained.
As a result this bug is being closed.
If the bug persists on a maintained version of gluster or against the mainline gluster repository, request that it be reopened and the Version field be marked appropriately.