This book provides information about installing, configuring, and maintaining Red Hat GFS (Red
Hat Global File System) for Red Hat Enterprise Linux 4.7.
Distribution of substantively modified versions of this document is prohibited without the explicit permission of the
copyright holder.
Distribution of the work or derivative of the work in any standard (paper) book form for commercial purposes is
prohibited unless prior permission is obtained from the copyright holder.
Red Hat and the Red Hat "Shadow Man" logo are registered trademarks of Red Hat, Inc. in the United States and other
countries.
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
1801 Varsity Drive
Raleigh, NC 27606-2072
USA
Phone: +1 919 754 3700
Phone: 888 733 4281
Fax: +1 919 754 3701
PO Box 13588
Research Triangle Park, NC 27709
USA
Global File System
Introduction .............................................................................................................. vii
1. Audience ...................................................................................................... vii
2. Related Documentation ................................................................................. vii
3. Document Conventions ................................................................................ viii
A. Upgrading GFS ....................................................................................................43
Index .......................................................................................................................47
vi
Introduction
Welcome to the Global File System Configuration and Administration document. This book
provides information about installing, configuring, and maintaining Red Hat GFS (Red Hat
Global File System). Red Hat GFS depends on the cluster infrastructure of Red Hat Cluster
Suite. For information about Red Hat Cluster Suite refer to Red Hat Cluster Suite Overview and
Configuring and Managing a Red Hat Cluster.
HTML and PDF versions of all the official Red Hat Enterprise Linux manuals and release notes
are available online at http://www.redhat.com/docs/.
1. Audience
This book is intended primarily for Linux system administrators who are familiar with the
following activities:
• Linux system administration procedures, including kernel configuration
• Installation and configuration of shared storage networks, such as Fibre Channel SANs
2. Related Documentation
For more information about using Red Hat Enterprise Linux, refer to the following resources:
• Red Hat Enterprise Linux Installation Guide — Provides information regarding installation of
Red Hat Enterprise Linux.
• Red Hat Enterprise Linux Introduction to System Administration — Provides introductory
information for new Red Hat Enterprise Linux system administrators.
• Red Hat Enterprise Linux System Administration Guide — Provides more detailed information
about configuring Red Hat Enterprise Linux to suit your particular needs as a user.
• Red Hat Enterprise Linux Reference Guide — Provides detailed information suited for more
experienced users to reference when needed, as opposed to step-by-step instructions.
• Red Hat Enterprise Linux Security Guide — Details the planning and the tools involved in
creating a secured computing environment for the data center, workplace, and home.
For more information about Red Hat Cluster Suite for Red Hat Enterprise Linux, refer to the
following resources:
• Red Hat Cluster Suite Overview — Provides a high level overview of the Red Hat Cluster
Suite.
• Configuring and Managing a Red Hat Cluster — Provides information about installing,
vii
Introduction
configuring and managing Red Hat Cluster components.
• LVM Administrator's Guide: Configuration and Administration — Provides a description of the
Logical Volume Manager (LVM), including information on running LVM in a clustered
environment.
• Using GNBD with Global File System — Provides an overview on using Global Network Block
Device (GNBD) with Red Hat GFS.
• Using Device-Mapper Multipath — Provides information about using the Device-Mapper
Multipath feature of Red Hat Enterprise Linux.
• Linux Virtual Server Administration — Provides information on configuring high-performance
systems and services with the Linux Virtual Server (LVS).
• Red Hat Cluster Suite Release Notes — Provides information about the current release of
Red Hat Cluster Suite.
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
3. 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. The categories include the
following:
Courier font
Courier font represents commands, file names and paths, and prompts .
When shown as below, it indicates computer output:
Bold Courier font represents text that you are to type, such as: service jonas start
If you have to run a command as root, the root prompt (#) precedes the command:
# gconftool-2
viii
Feedback
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.
In order of how critical the information is to you, these items are marked as follows:
Note
A note is typically information that you need to understand the behavior of the
system.
Tip
A tip is typically an alternative way of performing a task.
Important
Important information is necessary, but possibly unexpected, such as a
configuration change that will not persist after a reboot.
Caution
A caution indicates an act that would violate your support agreement, such as
recompiling the kernel.
Warning
A warning indicates potential data loss, as may happen when tuning hardware
for maximum performance.
ix
Introduction
4. 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)
By mentioning this manual's identifier, we know exactly which version of the guide you have.
If you have a suggestion for improving the documentation, try to be as specific as possible. If
you have found an error, please include the section number and some of the surrounding text
so we can find it easily.
5. Recommended References
For additional references about related topics, refer to the following table:
TopicReferenceComment
Shared Data Clustering and
File Systems
Storage Area Networks
(SANs)
Shared Data Clusters by Dilip
M. Ranade. Wiley, 2002.
Designing Storage Area
Networks: A Practical
Reference for Implementing
Fibre Channel and IP SANs,
Second Edition by Tom Clark.
Addison-Wesley, 2003.
Building SANs with Brocade
Fabric Switches by C.
Beauchamp, J. Judd, and B.
Keo. Syngress, 2001.
Building Storage Networks,
Second Edition by Marc
Farley. Osborne/McGraw-Hill,
2001.
Provides detailed technical
information on cluster file
system and cluster
volume-manager design.
Provides a concise summary
of Fibre Channel and IP SAN
Technology.
Best practices for building
Fibre Channel SANs based
on the Brocade family of
switches, including core-edge
topology for large SAN
fabrics.
Provides a comprehensive
overview reference on
storage networking
technologies.
Applications and High
Availability
x
Blueprints for High
Availability: Designing
Resilient Distributed Systems
Provides a summary of best
practices in high availability.
Recommended References
TopicReferenceComment
by E. Marcus and H. Stern.
Wiley, 2000.
Table 1. Recommended References Table
xi
xii
Chapter 1.
GFS Overview
Red Hat GFS is a cluster file system that is available with Red Hat Cluster Suite. Red Hat GFS
nodes are configured and managed with Red Hat Cluster Suite configuration and management
tools. Red Hat GFS provides data sharing among GFS nodes in a Red Hat cluster. GFS
provides a single, consistent view of the file-system name space across the GFS nodes in a
Red Hat cluster. GFS allows applications to install and run without much knowledge of the
underlying storage infrastructure. GFS is fully compliant with the IEEE POSIX interface, allowing
applications to perform file operations as if they were running on a local file system. Also, GFS
provides features that are typically required in enterprise environments, such as quotas, multiple
journals, and multipath support.
GFS provides a versatile method of networking your storage according to the performance,
scalability, and economic needs of your storage environment. This chapter provides some very
basic, abbreviated information as background to help you understand GFS. It contains the
following sections:
• Section 1, “Performance, Scalability, and Economy”
• Section 2, “GFS Functions”
• Section 3, “GFS Software Subsystems”
• Section 4, “Before Setting Up GFS”
1. Performance, Scalability, and Economy
You can deploy GFS in a variety of configurations to suit your needs for performance,
scalability, and economy. For superior performance and scalability, you can deploy GFS in a
cluster that is connected directly to a SAN. For more economical needs, you can deploy GFS in
a cluster that is connected to a LAN with servers that use GNBD (Global Network Block Device).
The following sections provide examples of how GFS can be deployed to suit your needs for
performance, scalability, and economy:
• Section 1.1, “Superior Performance and Scalability”
The deployment examples in this chapter reflect basic configurations; your needs
1
Chapter 1. GFS Overview
might require a combination of configurations shown in the examples.
1.1. Superior Performance and Scalability
You can obtain the highest shared-file performance when applications access storage directly.
The GFS SAN configuration in Figure 1.1, “GFS with a SAN” provides superior file performance
for shared files and file systems. Linux applications run directly on GFS nodes. Without file
protocols or storage servers to slow data access, performance is similar to individual Linux
servers with directly connected storage; yet, each GFS application node has equal access to all
data files. GFS supports over 300 GFS nodes.
Figure 1.1. GFS with a SAN
1.2. Performance, Scalability, Moderate Price
Multiple Linux client applications on a LAN can share the same SAN-based data as shown in
Figure 1.2, “GFS and GNBD with a SAN”. SAN block storage is presented to network clients as
block storage devices by GNBD servers. From the perspective of a client application, storage is
accessed as if it were directly attached to the server in which the application is running. Stored
data is actually on the SAN. Storage devices and data can be equally shared by network client
applications. File locking and sharing functions are handled by GFS for each network client.
2
Economy and Performance
Note
Clients implementing ext2 and ext3 file systems can be configured to access
their own dedicated slice of SAN storage.
Figure 1.2. GFS and GNBD with a SAN
1.3. Economy and Performance
Figure 1.3, “GFS and GNBD with Directly Connected Storage” shows how Linux client
applications can take advantage of an existing Ethernet topology to gain shared access to all
block storage devices. Client data files and file systems can be shared with GFS on each client.
Application failover can be fully automated with Red Hat Cluster Suite.
3
Chapter 1. GFS Overview
Figure 1.3. GFS and GNBD with Directly Connected Storage
2. GFS Functions
GFS is a native file system that interfaces directly with the VFS layer of the Linux kernel
file-system interface. GFS is a cluster file system that employs distributed metadata and multiple
journals for optimal operation in a cluster. Cluster management of GFS nodes is managed
through Red Hat Cluster Suite. Volume management is managed through CLVM (Cluster
Logical Volume Manager). For information about Red Hat Cluster Suite refer to Configuring and
Managing a Red Hat Cluster. For information about using CLVM, refer to LVM Administrator's
Guide.
Note
CLVM is a cluster-wide implementation of LVM, enabled by the CLVM daemon,
clvmd running in a Red Hat Cluster Suite cluster. The daemon makes it possible
to use LVM2 to manage logical volumes across a cluster, allowing all nodes in
the cluster to share the logical volumes.
GFS provides the following main functions:
4
• Making a File System
• Mounting a File System
• Unmounting a File System
• GFS Quota Management
• Growing a File System
• Adding Journals to a File System
• Direct I/O
• Data Journaling
• Configuring atime Updates
• Suspending Activity on a File System
GFS Software Subsystems
• Displaying Extended GFS Information and Statistics
gather a variety of information about the
file system.
lock_harness.koImplements a pluggable lock module
interface for GFS that allows for a variety
of locking mechanisms to be used (for
example, the DLM lock module,
lock_dlm.ko).
lock_dlm.koA lock module that implements DLM
locking for GFS. It plugs into the lock
harness, lock_harness.ko and
communicates with the DLM lock
manager in Red Hat Cluster Suite.
lock_gulm.koA lock module that implements GULM
locking for GFS. It plugs into the lock
harness, lock_harness.ko and
communicates with the GULM lock
manager in Red Hat Cluster Suite.
lock_nolock.koA lock module for use when GFS is used
as a local file system only. It plugs into
the lock harness, lock_harness.ko and
provides local locking.
Table 1.1. GFS Software Subsystem Components
4. Before Setting Up GFS
Before you install and set up GFS, note the following key characteristics of your GFS file
systems:
Number of file systems
Determine how many GFS file systems to create initially. (More file systems can be added
later.)
File-system name
Determine a unique name for each file system. Each file-system name is required in the
form of a parameter variable. For example, this book uses file-system names gfs1 and
gfs2 in some example procedures.
Journals
Determine the number of journals for your GFS file systems. One journal is required for
each node that mounts a GFS file system. Make sure to account for additional journals
needed for future expansion.
6
Loading...
+ 42 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.