Table of Contents
Advertisement
Chapter 3. GNBD Driver and
The Global Network Block Device (GNBD) driver allows a node to export its local storage as a
GNBD over a network so that other nodes on the network can share the storage. Client nodes
importing the GNBD use it like any other block device. Importing a GNBD on multiple clients
forms a shared storage configuration through which GFS can be used.
The GNBD driver is implemented through the following components.
•
— Implements the GNBD server. It is a user-space daemon that allows a node to
gnbd_serv
export local storage over a network.
•
— Implements the GNBD device driver on GNBD clients (nodes using GNBD
gnbd.ko
devices).
Two user commands are available to configure GNBD:
•
(for servers) — User program for creating, exporting, and managing GNBDs on
gnbd_export
a GNBD server.
•
(for clients) — User program for importing and managing GNBDs on a GNBD
gnbd_import
client.
1. Exporting a GNBD from a Server
The
daemon must be running on a node before it can export storage as a GNBD. You
gnbd_serv
can start the
gnbd_serv
#gnbd_serv
gnbd_serv: startup succeeded
Once local storage has been identified to be exported, the
port it.
Warning
When you configure GNBD servers with device-mapper multipath, you must not
use page caching. All GNBDs that are part of a logical volume must run with
caching disabled. By default, the
turned off.
Command Usage
daemon running
gnbd_serv
as follows:
gnbd_export
command exports with caching
gnbd_export
3
command is used to ex-
Advertisement
Table of Contents
Need help?
Do you have a question about the GNBD WITH GLOBAL FILE SYSTEM IN RHEL 4.5 and is the answer not in the manual?
Questions and answers