[Gluster-users] What is the CLI NUFA option "local-volume-name" good for?

[Jeff Darcy]

On Fri, Apr 28, 2017, at 10:57 AM, Jan Wrona wrote:
> I've been struggling with NUFA for a while now and I know very well what 
> the "option local-volume-name brick" in the volfile does. In fact, I've 
> been using a filter to force gluster to use the local subvolume I want 
> instead of the first local subvolume it finds, but filters are very 
> unreliable. Recently I've found this bug [1] and thought that I'll 
> finally be able to set the NUFA's "local-volume-name" option 
> *per-server* through the CLI without the use of the filter, but no. This 
> options sets the value globally, so I'm asking what is the use of LOCAL 
> volume name set GLOBALLY with the same value on every server?

You're right that it would be a bit silly to set this using "gluster
volume set" but it makes much more sense as a command-line override
using "--xlator-option" instead.  Then it could in fact be different on
every client, even though it's not even set in the volfile.