ganesha-config man page

ganesha-config ā€” NFS Ganesha Configuration File

Synopsis

/etc/ganesha/ganesha.conf

Description

NFS-Ganesha obtains configuration data from the configuration file:

/etc/ganesha/ganesha.conf

The configuration file consists of following parts:

Comments

Empty lines and lines starting with '#' are comments.:

# This whole line is a comment
Protocol = TCP; # The rest of this line is a comment

Blocks

Related options are grouped together into "blocks". A block is a name followed by parameters enclosed between "{" and "}". A block can contain other sub blocks as well.:

EXPORT
{
    Export_ID = 1;
    FSAL {
        Name = VFS:
    }
}

NOTE: FSAL is a sub block. Refer to Blocks section for list of blocks and options.

Options

Configuration options can be of following types.

1. Numeric. Numeric options can be defined in octal, decimal, or hexadecimal. The format follows ANSI C syntax. eg.:

mode = 0755;  # This is octal 0755, 493 (decimal)

Numeric values can also be negated or logical NOT'd. eg.:

anonymousuid = -2; # this is a negative
mask = ~0xff; # Equivalent to 0xffffff00 (for 32 bit integers)

2. Boolean. Possible values are true, false, yes and no. 1 and 0 are not acceptable.

3. List. The option can contain a list of possible applicable values. Protocols = 3, 4, 9p;

Including other config files

Additional files can be referenced in a configuration using '%include' and '%url' directives.:

%include <filename>
%url <url, e.g., rados://mypool/mynamespace/myobject>

The included file is inserted into the configuration text in place of the %include or %url line. Sub-inclusions may be to any depth. Filenames and URLs may optionally use '"':

%include base.conf
%include "base.conf"
%url rados://mypool/mynamespace/myobject
%url "rados://mypool/mynamespace/myobject"
%url rados://mypool/myobject
%url "rados://mypool/myobject"

In the case of rados:// URLs, providing a two-component URL indicates that the default namespace should be used.

Blocks

NFS-Ganesha supports the following blocks:

Export {}

Along with its configuration options, the EXPORT block supports FSAL and CLIENT sub-blocks. See ganesha-export-config(8) for usage of this block and its sub-blocks.

Export_defaults {}

Refer to ganesha-export-config(8) for usage

Mdcache {}

Refer to ganesha-cache-config(8) for usage

Nfs_core_param {}

Refer to ganesha-core-config(8) for usage

Nfs_ip_name {}

Refer to ganesha-core-config(8) for usage

Nfs_krb5 {}

Refer to ganesha-core-config(8) for usage

NFSv4 {}

Refer to ganesha-core-config(8) for usage

Ceph {}

Refer to ganesha-ceph-config(8) for usage

9P {}

Refer to ganesha-9p-config(8) for usage

Gluster {}

Refer to ganesha-gluster-config(8) for usage

GPFS {}

Refer to ganesha-gpfs-config(8) for usage

Log {}

Refer to ganesha-log-config(8) for usage

1.**LOG { FACILITY {} }** 2.**LOG { FORMAT {} }**

Proxy {}

Refer to ganesha-proxy-config(8) for usage

RGW {}

Refer to ganesha-rgw-config(8) for usage

VFS {}

Refer to ganesha-vfs-config(8) for usage

XFS {}

Refer to ganesha-xfs-config(8) for usage

Example

Along with "ganesha.conf", for each installed FSAL, a sample config file is added at:

/etc/ganesha

See Also

ganesha-log-config(8) ganesha-rgw-config(8) ganesha-vfs-config(8) ganesha-lustre-config(8) ganesha-xfs-config(8) ganesha-gpfs-config(8) ganesha-gluster-config(8) ganesha-9p-config(8) ganesha-proxy-config(8) ganesha-ceph-config(8) ganesha-core-config(8) ganesha-export-config(8)

Referenced By

ganesha-cache-config(8), ganesha-ceph-config(8), ganesha-export-config(8), ganesha-log-config(8).

Feb 20, 2020 NFS-Ganesha