Red Hat GFS 6.0 Administrator's Manual page 136

122
Note
A server should not import the GNBDs to use them as a client would. If a server exports the devices
uncached, they may also be used by
11.1.1.1. Usage
gnbd_export -d pathname -e gnbdname [
pathname
Specifies a storage device to export.
gnbdname
Specifies an arbitrary name selected for the GNBD. It is used as the device name on GNBD
clients. This name must be unique among all GNBDs exported in the network.
-o
Export the device as read-only.
Note
If a GNBD server that is exporting CCS files is also exporting GNBDs in multipath mode, it
must export the CCS files as read-only. Under those circumstances, a GNBD client cannot use
to update its copy of the CCS files. Instead, the CCS files must be updated on a node
ccs_tool
where the CCS files are stored locally or on FC-attached storage.
-c
Enable caching. Reads from the exported GNBD and takes advantage of the Linux page cache.
By default, the
gnbd_export
Caution
For GNBD multipath, you must not specify the
must run with caching disabled . Pool, the GFS volume manager, does not check for caching
being disabled; therefore, data corruption will occur if the GNBD devices are run with caching
enabled.
Note
If you have been using GFS 5.2 or earlier and do not want to change your GNBD setup you
should specify the
for
gnbd_export
decrease. Also, if the
using the default timeout value (the
command and its options, see the
and
ccsd
-c
command does not enable caching.
option. Before GFS Release 5.2.1, Linux caching was enabled by default
-c
. If the option is not specified, GNBD runs with a noticeable performance
-c
option is not specified, the exported GNBD runs in timeout mode,
-c
-t
gnbd_export
.
gfs
]
]
option. All GNBDs that are part of the pool
-c
option). For more information about the
man page.
Chapter 11. Using GNBD
gnbd_export