ganesha-export-config(8)

1GANESHA-EXPORT-CONFIG(8)          NFS-Ganesha         GANESHA-EXPORT-CONFIG(8)
2
3
4

NAME

6       ganesha-export-config - NFS Ganesha Export Configuration File
7

SYNOPSIS

9          /etc/ganesha/ganesha.conf
10

DESCRIPTION

12       NFS-Ganesha obtains configuration data from the configuration file:
13          /etc/ganesha/ganesha.conf
14
15       This file lists NFS-Ganesha Export block config options.
16
17   EXPORT_DEFAULTS {}
18       These  options  are  all  "export  permissions"  options,  and  will be
19       repeated in the EXPORT {} and EXPORT { CLIENT {} } blocks.
20
21       These options will all be dynamically updateable.
22
23       Access_Type(enum, default None)
24
25              Possible values:
26                     None, RW, RO, MDONLY, MDONLY_RO
27
28       Protocols(enum list, default [3,4])
29
30              Possible values:
31                     3, 4, NFS3, NFS4, V3, V4, NFSv3, NFSv4, 9P
32
33       Transports(enum list, values [UDP, TCP, RDMA], default [UDP, TCP])
34
35       Anonymous_uid(anonid, range INT32_MIN to UINT32_MAX, default -2)
36
37       Anonymous_gid(anonid, range INT32_MIN to UINT32_MAX, default -2)
38
39       SecType(enum list, default [none, sys])
40
41              Possible values:
42                     none, sys, krb5, krb5i, krb5p
43
44       PrivilegedPort(bool, default false)
45
46       Manage_Gids(bool, default false)
47
48       Squash(enum, default root_sqaush)
49
50              Possible values:
51                     root, root_squash,  rootsquash,  rootid,  root_id_squash,
52                     rootidsquash, all, all_squash, allsquash, all_anomnymous,
53                     allanonymous, no_root_squash, none, noidsquash
54
55              Each line of defaults above are synonyms
56
57       NFS_Commit(bool, default false)
58
59       Delegations(enum, default None)
60
61              Possible values:
62                     None, read, write, readwrite, r, w, rw
63
64       Attr_Expiration_Time(int32, range -1 to INT32_MAX, default 60)
65
66   EXPORT {}
67       Export_id (required):
68              An identifier for the export, must be unique and betweem  0  and
69              65535.   If  Export_Id  0  is specified, Pseudo must be the root
70              path (/).
71
72       Path (required)
73              The directory in the exported file system this export is  rooted
74              on  (may  be  ignored  for some FSALs). It need not be unique if
75              Pseudo and/or Tag are specified.
76
77              Note  that  if  it  is  not  unique,   and   the   core   option
78              mount_path_pseudo  is  not  set  true, a v3 mount using the path
79              will ONLY be able to access  the  first  export  configured.  To
80              access other exports the Tag option would need to be used.
81
82       Pseudo (required v4)
83              This  option specifies the position in the Pseudo FS this export
84              occupies if this is an NFS v4 export.  It  must  be  unique.  By
85              using  different  Pseudo  options, the same Path may be exported
86              multiple times.
87
88              This option is used to place the export within the NFS v4 Pseudo
89              Filesystem. This creates a single name space for NFS v4. Clients
90              may mount the root of the  Pseudo  Filesystem  and  navigate  to
91              exports.  Note that the Path and Tag options are not at all vis‐
92              ible to NFS v4 clients.
93
94              Export id 0 is automatically created to provide the root and any
95              directories  necessary  to  navigate  to  exports if there is no
96              other export specified with Pseudo = /;. Note that if an  export
97              is specified with Pseudo = /;, it need not be export id 0. Spec‐
98              ifying such an export with FSAL { name = PSEUDO; } may  be  used
99              to  create a Pseudo FS with specific options. Such an export may
100              also use other FSALs (though directories to reach  exports  will
101              ONLY be automatically created on FSAL PSEUDO exports).
102
103       Tag (no default)
104              This  option allows an alternative access for NFS v3 mounts. The
105              option MUST not have a leading /. Clients may not  mount  subdi‐
106              rectories (i.e. if Tag = foo, the client may not mount foo/baz).
107              By using different Tag options, the same Path  may  be  exported
108              multiple times.
109
110       MaxRead (64*1024*1024)
111              The maximum read size on this export
112
113       MaxWrite (64*1024*1024)
114              The maximum write size on this export
115
116       PrefRead (64*1024*1024)
117              The preferred read size on this export
118
119       PrefWrite (64*1024*1024)
120              The preferred write size on this export
121
122       PrefReaddir (16384)
123              The preferred readdir size on this export
124
125       MaxOffsetWrite (INT64_MAX)
126              Maximum  file  offset  that  may  be  written  Range  is  512 to
127              UINT64_MAX
128
129       MaxOffsetRead (INT64_MAX)
130              Maximum file offset that may be read Range is 512 to UINT64_MAX
131
132       CLIENT (optional)
133              See the EXPORT { CLIENT  {} } block.
134
135       FSAL (required)
136              See the EXPORT { FSAL  {} } block.
137
138   EXPORT { CLIENT {} }
139       Take all the "export permissions" options  from  EXPORT_DEFAULTS.   The
140       client lists are dynamically updateable.
141
142       Clients(client list, empty)
143              Client  list  entries  can  take  on one of the following forms:
144              Match any client:
145
146                 @name       Netgroup name
147                 x.x.x.x/y   IPv4 network address
148                 wildcarded  If the string contains at least one ? or *
149                             character (and is not simply "*"), the string is
150                             used to pattern match host names. Note that [] may
151                             also be used, but the pattern MUST have at least one
152                             ? or *
153                 hostname    Match a single client (match is by IP address, all
154                             addresses returned by getaddrinfo will match, the
155                             getaddrinfo call is made at config parsing time)
156                 IP address  Match a single client
157
158   EXPORT { FSAL {} }
159       NFS-Ganesha supports the following FSALs: Ceph Gluster GPFS  Proxy  RGW
160       VFS LUSTRE
161
162       Refer to individual FSAL config file for list of config options.
163

NAME

SYNOPSIS

DESCRIPTION

SEE ALSO