Related Manuals for Red Hat GNBD WITH GLOBAL FILE SYSTEM 4.7
Summary of Contents for Red Hat GNBD WITH GLOBAL FILE SYSTEM 4.7
- Page 1 Using GNBD with Global File System Configuration and Administration Global_Network_Block_Device ISBN: N/A Publication date: July 2008...
- Page 2 Using GNBD with Global File System This book provides an overview on using Global Network Block Device (GNBD) with Red Hat GFS for Red Hat Enterprise Linux 4.7.
- Page 3 All other trademarks referenced herein are the property of their respective owners. The GPG fingerprint of the security@redhat.com key is: CA 20 86 86 2B D6 9D FC 65 F6 EC C4 21 91 80 CD DB 42 A6 0E...
- Page 4 Using GNBD with Global File System...
-
Page 5: Table Of Contents
Introduction ......................vii 1. About This Guide ..................vii 2. Audience ...................... vii 3. Software Versions ..................vii 4. Related Documentation ................. vii 5. Document Conventions ................viii 6. Feedback .......................x 1. Using GNBD with Red Hat GFS ................1 2. -
Page 7: Introduction
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. -
Page 8: Document Conventions
Red Hat Cluster Suite documentation and other Red Hat documents are available in HTML and PDF versions online at the following location: http://www.redhat.com/docs 5. Document Conventions Certain words in this manual are represented in different fonts, styles, and weights. This highlighting indicates that the word is part of a specific category. - Page 9 Document Conventions # gconftool-2 italic Courier font Italic Courier font represents a variable, such as an installation directory: install_dir/bin/ bold font Bold font represents application programs and text found on a graphical interface. When shown like this: OK , it indicates a button on a graphical application interface. Additionally, the manual uses different strategies to draw your attention to pieces of information.
-
Page 10: Feedback
6. 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: rh-gfs(EN)-4.7 (2008-07-24T15:10) -
Page 11: Using Gnbd With Red Hat Gfs
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. -
Page 13: Considerations For Using Gnbd With Device-Mapper Multipath
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. -
Page 15: Gnbd Driver And Command Usage
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. - Page 16 Chapter 3. GNBD Driver and Command Usage Note A server should not import the GNBDs to use them as a client would. If a server exports the devices uncached, the underlying devices may also be used by Usage gnbd_export -dpathname-egnbdname [-c][-u][-U pathname Specifies a storage device to export.
- Page 17 Examples -uuid Manually sets the Universal Identifier for an exported device. This option is used with The UID is used by device-mapper multipath to determine which devices belong in a multipath map. A device must have a UID to be multipathed. However, for most SCSI devices the default Get UID command, , will return an /usr/sbin/gnbd_get_uid...
-
Page 18: Importing A Gnbd On A Client
Chapter 3. GNBD Driver and Command Usage gnbd_export -d /dev/sdb1 -e delta -c This example exports device as GNBD with cache enabled. /dev/sdb2 delta gnbd_export -d /dev/sdb2 -e delta -c 2. Importing a GNBD on a Client kernel module must be loaded on a node before it can import GNBDs. When gnbd.ko GNBDs are imported, device nodes are created for them in with the name... -
Page 19: Running Gfs On A Gnbd Server Node
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. -
Page 21: Index
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, 8 exporting from a server daemon, 5 feedback, x, x fencing GNBD server nodes, 3 GFS, using on a GNBD server node, 9 GNBD, using with Red Hat GFS, 1 gnbd.ko module, 5, 8...