Introduction 1. About This Guide This book describes how to use Global Network Block Device (GNDB) with Global File System (GFS), including information about device-mapper multipath, GNDB driver and command usage, and running GFS on a GNBD server node. 2. Audience This book is intended to be used by system administrators managing systems running the Linux operating system.
5. Feedback If you spot a typo, or if you have thought of a way to make this manual better, we would love to hear from you. Please submit a report in Bugzilla (http://bugzilla.redhat.com/bugzilla/) against the component rh-cs. Be sure to mention the manual's identifier:...
Typographic Conventions The above includes a file name, a shell command and a key cap, all presented in Mono-spaced Bold and all distinguishable thanks to context. Key-combinations can be distinguished from key caps by the hyphen connecting each part of a key- combination.
Introduction The mount -o remount file-system command remounts the named file system. For example, to remount the /home file system, the command is mount -o remount /home. To see the version of a currently installed package, use the rpm -q package command.
Notes and Warnings 6.3. Notes and Warnings Finally, we use three visual styles to draw attention to information that might otherwise be overlooked. Note A Note is a tip or shortcut or alternative approach to the task at hand. Ignoring a note should have no negative consequences, but you might miss out on a trick that makes your life easier.
Chapter 1. Using GNBD with Red Hat GFS GNBD (Global Network Block Device) provides block-level storage access over an Ethernet LAN. GNBD components run as a client in a GFS node and as a server in a GNBD server node. A GNBD server node exports block-level storage from its local storage (either directly attached storage or SAN storage) to a GFS node.
Chapter 2. Considerations for Using GNBD with Device-Mapper Multipath GNBD with device-mapper multipath allows you to configure multiple GNBD server nodes (nodes that export GNBDs to GFS nodes) to provide redundant paths to the storage devices. The GNBD server nodes, in turn, present multiple storage paths to GFS nodes via redundant GNBDs. When using GNBD with device-mapper multipath, if a GNBD server node becomes unavailable, another GNBD server node can provide GFS nodes with access to storage devices.
Chapter 3. GNBD Driver and Command Usage 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.
Chapter 3. GNBD Driver and Command Usage 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 a network. Export the device as read-only.
Examples -U Command Gets the UID command. The UID command is a command the gnbd_export command will run to get a Universal Identifier for the exported device. The UID is necessary to use device-mapper multipath with GNBD. The command must use the full path of any executeable that you wish to run.
Chapter 4. Running GFS on a GNBD Server Node You can run GFS on a GNBD server node, with some restrictions. In addition, running GFS on a GNBD server node reduces performance. The following restrictions apply when running GFS on a GNBD server node.
Index device-mapper multipath, 3 fencing GNBD server nodes, 3 Linux page caching, 3 driver and command usage, 5 exporting from a server, 5 importing on a client, 7 exporting from a server daemon, 5 feedback, vi, vi fencing GNBD server nodes, 3 GFS, using on a GNBD server node, 9 GNBD, using with Red Hat GFS, 1 gnbd.ko module, 5, 7...