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 re‐
19       peated 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       Security_Label(bool, default false)
58
59       NFS_Commit(bool, default false)
60
61       Delegations(enum, default None)
62
63              Possible values:
64                     None, read, write, readwrite, r, w, rw
65
66       Attr_Expiration_Time(int32, range -1 to INT32_MAX, default 60)
67
68   EXPORT {}
69       Export_id (required):
70              An identifier for the export, must be unique and betweem  0  and
71              65535.   If  Export_Id  0  is specified, Pseudo must be the root
72              path (/).
73
74       Path (required)
75              The directory in the exported file system this export is  rooted
76              on  (may  be  ignored  for some FSALs). It need not be unique if
77              Pseudo and/or Tag are specified.
78
79              Note  that  if  it  is  not  unique,   and   the   core   option
80              mount_path_pseudo  is  not  set  true, a v3 mount using the path
81              will ONLY be able to access the first export configured. To  ac‐
82              cess other exports the Tag option would need to be used.
83
84       Pseudo (required v4)
85              This  option specifies the position in the Pseudo FS this export
86              occupies if this is an NFS v4 export. It must be unique. By  us‐
87              ing different Pseudo options, the same Path may be exported mul‐
88              tiple times.
89
90              This option is used to place the export within the NFS v4 Pseudo
91              Filesystem. This creates a single name space for NFS v4. Clients
92              may mount the root of the Pseudo Filesystem and navigate to  ex‐
93              ports.   Note that the Path and Tag options are not at all visi‐
94              ble to NFS v4 clients.
95
96              Export id 0 is automatically created to provide the root and any
97              directories  necessary  to  navigate  to  exports if there is no
98              other export specified with Pseudo = /;. Note that if an  export
99              is specified with Pseudo = /;, it need not be export id 0. Spec‐
100              ifying such an export with FSAL { name = PSEUDO; } may  be  used
101              to  create a Pseudo FS with specific options. Such an export may
102              also use other FSALs (though directories to reach  exports  will
103              ONLY be automatically created on FSAL PSEUDO exports).
104
105       Tag (no default)
106              This  option allows an alternative access for NFS v3 mounts. The
107              option MUST not have a leading /. Clients may not  mount  subdi‐
108              rectories (i.e. if Tag = foo, the client may not mount foo/baz).
109              By using different Tag options, the same Path  may  be  exported
110              multiple times.
111
112       MaxRead (64*1024*1024)
113              The maximum read size on this export
114
115       MaxWrite (64*1024*1024)
116              The maximum write size on this export
117
118       PrefRead (64*1024*1024)
119              The preferred read size on this export
120
121       PrefWrite (64*1024*1024)
122              The preferred write size on this export
123
124       PrefReaddir (16384)
125              The preferred readdir size on this export
126
127       MaxOffsetWrite (INT64_MAX)
128              Maximum  file  offset  that  may  be  written  Range  is  512 to
129              UINT64_MAX
130
131       MaxOffsetRead (INT64_MAX)
132              Maximum file offset that may be read Range is 512 to UINT64_MAX
133
134       CLIENT (optional)
135              See the EXPORT { CLIENT  {} } block.
136
137       FSAL (required)
138              See the EXPORT { FSAL  {} } block.
139
140   EXPORT { CLIENT {} }
141       Take all the "export permissions" options  from  EXPORT_DEFAULTS.   The
142       client lists are dynamically updateable.
143
144       Clients(client list, empty)
145              Client  list  entries  can  take  on one of the following forms:
146              Match any client:
147
148                 @name       Netgroup name
149                 x.x.x.x/y   IPv4 network address
150                 wildcarded  If the string contains at least one ? or *
151                             character (and is not simply "*"), the string is
152                             used to pattern match host names. Note that [] may
153                             also be used, but the pattern MUST have at least one
154                             ? or *
155                 hostname    Match a single client (match is by IP address, all
156                             addresses returned by getaddrinfo will match, the
157                             getaddrinfo call is made at config parsing time)
158                 IP address  Match a single client
159
160   EXPORT { FSAL {} }
161       NFS-Ganesha supports the following FSALs: Ceph Gluster GPFS  Proxy  RGW
162       VFS LUSTRE
163
164       Refer to individual FSAL config file for list of config options.
165

NAME

SYNOPSIS

DESCRIPTION

SEE ALSO