搜索

第 1 章 GFS2 总​​​​​​​览​​​​​​​

download PDF
红​​​​​​​帽​​​​​​​ GFS2 文​​​​​​​件​​​​​​​系​​​​​​​统​​​​​​​是​​​​​​​固​​​​​​​有​​​​​​​文​​​​​​​件​​​​​​​系​​​​​​​统​​​​​​​,直​​​​​​​接​​​​​​​和​​​​​​​ Linux 内​​​​​​​核​​​​​​​文​​​​​​​件​​​​​​​系​​​​​​​统​​​​​​​界​​​​​​​面​​​​​​​(VFS 层​​​​​​​)相​​​​​​​接​​​​​​​。​​​​​​​GFS2 文​​​​​​​件​​​​​​​系​​​​​​​统​​​​​​​可​​​​​​​作​​​​​​​为​​​​​​​单​​​​​​​独​​​​​​​的​​​​​​​系​​​​​​​统​​​​​​​使​​​​​​​用​​​​​​​,也​​​​​​​可​​​​​​​作​​​​​​​为​​​​​​​群​​​​​​​集​​​​​​​配​​​​​​​置​​​​​​​的​​​​​​​一​​​​​​​部​​​​​​​分​​​​​​​。​​​​​​​当​​​​​​​作​​​​​​​为​​​​​​​群​​​​​​​集​​​​​​​文​​​​​​​件​​​​​​​系​​​​​​​统​​​​​​​使​​​​​​​用​​​​​​​时​​​​​​​,GFS2 采​​​​​​​用​​​​​​​分​​​​​​​布​​​​​​​式​​​​​​​元​​​​​​​数​​​​​​​据​​​​​​​和​​​​​​​多​​​​​​​日​​​​​​​志​​​​​​​。​​​​​​​
A GFS2 file system can be created on an LVM logical volume. A logical volume is an aggregation of underlying block devices that appears as a single logical device. For information on the LVM volume manager, see the LVM Administrator's Guide.
GFS2 是​​​​​​​基​​​​​​​于​​​​​​​ 64 位​​​​​​​构​​​​​​​架​​​​​​​,理​​​​​​​论​​​​​​​上​​​​​​​可​​​​​​​提​​​​​​​供​​​​​​​ 8 EB 文​​​​​​​件​​​​​​​系​​​​​​​统​​​​​​​。​​​​​​​但​​​​​​​是​​​​​​​,目​​​​​​​前​​​​​​​支​​​​​​​持​​​​​​​的​​​​​​​最​​​​​​​大​​​​​​​ GFS2 文​​​​​​​件​​​​​​​系​​​​​​​统​​​​​​​为​​​​​​​ 25 TB。​​​​​​​如​​​​​​​果​​​​​​​您​​​​​​​的​​​​​​​系​​​​​​​统​​​​​​​要​​​​​​​求​​​​​​​使​​​​​​​用​​​​​​​ 25 TB 以​​​​​​​上​​​​​​​的​​​​​​​ GFS2 文​​​​​​​件​​​​​​​系​​​​​​​统​​​​​​​,请​​​​​​​联​​​​​​​络​​​​​​​您​​​​​​​的​​​​​​​红​​​​​​​帽​​​​​​​服​​​​​​​务​​​​​​​代​​​​​​​表​​​​​​​。​​​​​​​
当​​​​​​​决​​​​​​​定​​​​​​​您​​​​​​​的​​​​​​​文​​​​​​​件​​​​​​​系​​​​​​​统​​​​​​​大​​​​​​​小​​​​​​​时​​​​​​​,您​​​​​​​应​​​​​​​该​​​​​​​考​​​​​​​虑​​​​​​​您​​​​​​​的​​​​​​​恢​​​​​​​复​​​​​​​需​​​​​​​求​​​​​​​。​​​​​​​在​​​​​​​一​​​​​​​个​​​​​​​很​​​​​​​大​​​​​​​的​​​​​​​文​​​​​​​件​​​​​​​系​​​​​​​统​​​​​​​中​​​​​​​运​​​​​​​行​​​​​​​fsck 命​​​​​​​令​​​​​​​需​​​​​​​要​​​​​​​很​​​​​​​长​​​​​​​时​​​​​​​间​​​​​​​且​​​​​​​消​​​​​​​耗​​​​​​​大​​​​​​​量​​​​​​​内​​​​​​​存​​​​​​​。​​​​​​​另​​​​​​​外​​​​​​​,在​​​​​​​磁​​​​​​​盘​​​​​​​或​​​​​​​者​​​​​​​磁​​​​​​​盘​​​​​​​子​​​​​​​系​​​​​​​统​​​​​​​失​​​​​​​败​​​​​​​事​​​​​​​件​​​​​​​中​​​​​​​,恢​​​​​​​复​​​​​​​时​​​​​​​间​​​​​​​受​​​​​​​您​​​​​​​的​​​​​​​备​​​​​​​份​​​​​​​介​​​​​​​质​​​​​​​速​​​​​​​度​​​​​​​的​​​​​​​限​​​​​​​制​​​​​​​。​​​​​​​
当​​​​​​​在​​​​​​​红​​​​​​​帽​​​​​​​群​​​​​​​集​​​​​​​套​​​​​​​件​​​​​​​中​​​​​​​进​​​​​​​行​​​​​​​配​​​​​​​置​​​​​​​时​​​​​​​,可​​​​​​​使​​​​​​​用​​​​​​​红​​​​​​​帽​​​​​​​群​​​​​​​集​​​​​​​套​​​​​​​件​​​​​​​配​​​​​​​置​​​​​​​和​​​​​​​管​​​​​​​理​​​​​​​工​​​​​​​具​​​​​​​配​​​​​​​置​​​​​​​和​​​​​​​管​​​​​​​理​​​​​​​红​​​​​​​帽​​​​​​​ GFS2 节​​​​​​​点​​​​​​​。​​​​​​​然​​​​​​​后​​​​​​​红​​​​​​​帽​​​​​​​ GFS2 会​​​​​​​提​​​​​​​供​​​​​​​在​​​​​​​红​​​​​​​帽​​​​​​​群​​​​​​​集​​​​​​​的​​​​​​​ GFS2 节​​​​​​​点​​​​​​​间​​​​​​​共​​​​​​​享​​​​​​​的​​​​​​​数​​​​​​​据​​​​​​​,即​​​​​​​在​​​​​​​ GFS2 节​​​​​​​点​​​​​​​间​​​​​​​单​​​​​​​一​​​​​​​、​​​​​​​一​​​​​​​致​​​​​​​的​​​​​​​文​​​​​​​件​​​​​​​系​​​​​​​统​​​​​​​名​​​​​​​称​​​​​​​查​​​​​​​看​​​​​​​。​​​​​​​这​​​​​​​样​​​​​​​就​​​​​​​允​​​​​​​许​​​​​​​不​​​​​​​同​​​​​​​节​​​​​​​点​​​​​​​中​​​​​​​的​​​​​​​进​​​​​​​程​​​​​​​可​​​​​​​以​​​​​​​与​​​​​​​在​​​​​​​本​​​​​​​地​​​​​​​文​​​​​​​件​​​​​​​系​​​​​​​统​​​​​​​中​​​​​​​同​​​​​​​一​​​​​​​节​​​​​​​点​​​​​​​中​​​​​​​的​​​​​​​进​​​​​​​程​​​​​​​相​​​​​​​同​​​​​​​的​​​​​​​方​​​​​​​法​​​​​​​共​​​​​​​享​​​​​​​ GFS2 文​​​​​​​件​​​​​​​,其​​​​​​​中​​​​​​​没​​​​​​​有​​​​​​​明​​​​​​​显​​​​​​​的​​​​​​​差​​​​​​​别​​​​​​​。​​​​​​​有​​​​​​​关​​​​​​​红​​​​​​​帽​​​​​​​群​​​​​​​集​​​​​​​套​​​​​​​件​​​​​​​的​​​​​​​详​​​​​​​情​​​​​​​请​​​​​​​参​​​​​​​考​​​​​​​《​​​​​​​配​​​​​​​置​​​​​​​和​​​​​​​管​​​​​​​理​​​​​​​红​​​​​​​帽​​​​​​​群​​​​​​​集​​​​​​​》​​​​​​​。​​​​​​​
LVM logical volumes in a Red Hat Cluster suite are managed with CLVM, which 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. to any directory on your system. For information on the LVM volume manager, see the LVM Administrator's Guide.
gfs2.ko 内​​​​​​​核​​​​​​​模​​​​​​​块​​​​​​​部​​​​​​​署​​​​​​​ GFS2 文​​​​​​​件​​​​​​​系​​​​​​​统​​​​​​​,并​​​​​​​在​​​​​​​ GFS2 群​​​​​​​集​​​​​​​节​​​​​​​点​​​​​​​中​​​​​​​载​​​​​​​入​​​​​​​。​​​​​​​
本​​​​​​​章​​​​​​​提​​​​​​​供​​​​​​​一​​​​​​​些​​​​​​​作​​​​​​​为​​​​​​​背​​​​​​​景​​​​​​​资​​​​​​​料​​​​​​​的​​​​​​​基​​​​​​​本​​​​​​​简​​​​​​​短​​​​​​​资​​​​​​​料​​​​​​​以​​​​​​​便​​​​​​​帮​​​​​​​助​​​​​​​您​​​​​​​了​​​​​​​解​​​​​​​ GFS2,其​​​​​​​中​​​​​​​包​​​​​​​括​​​​​​​以​​​​​​​下​​​​​​​部​​​​​​​分​​​​​​​:

1.1. 设​​​​​​​定​​​​​​​ GFS2 前​​​​​​​

在​​​​​​​您​​​​​​​安​​​​​​​装​​​​​​​和​​​​​​​设​​​​​​​定​​​​​​​ GFS2 之​​​​​​​前​​​​​​​,请​​​​​​​记​​​​​​​录​​​​​​​您​​​​​​​的​​​​​​​ GFS2 文​​​​​​​件​​​​​​​系​​​​​​​统​​​​​​​的​​​​​​​以​​​​​​​下​​​​​​​重​​​​​​​要​​​​​​​特​​​​​​​性​​​​​​​:
GFS 节​​​​​​​点​​​​​​​
决​​​​​​​定​​​​​​​红​​​​​​​帽​​​​​​​群​​​​​​​集​​​​​​​套​​​​​​​件​​​​​​​中​​​​​​​的​​​​​​​哪​​​​​​​个​​​​​​​节​​​​​​​点​​​​​​​将​​​​​​​挂​​​​​​​载​​​​​​​ GFS2 文​​​​​​​件​​​​​​​系​​​​​​​统​​​​​​​。​​​​​​​
文​​​​​​​件​​​​​​​系​​​​​​​统​​​​​​​数​​​​​​​
决​​​​​​​定​​​​​​​最​​​​​​​初​​​​​​​创​​​​​​​建​​​​​​​多​​​​​​​少​​​​​​​个​​​​​​​ GFS2 文​​​​​​​件​​​​​​​系​​​​​​​统​​​​​​​(以​​​​​​​后​​​​​​​可​​​​​​​以​​​​​​​添​​​​​​​加​​​​​​​更​​​​​​​多​​​​​​​的​​​​​​​文​​​​​​​件​​​​​​​系​​​​​​​统​​​​​​​)。​​​​​​​
文​​​​​​​件​​​​​​​系​​​​​​​统​​​​​​​名​​​​​​​称​​​​​​​
为​​​​​​​每​​​​​​​个​​​​​​​文​​​​​​​件​​​​​​​系​​​​​​​统​​​​​​​决​​​​​​​定​​​​​​​一​​​​​​​个​​​​​​​特​​​​​​​定​​​​​​​的​​​​​​​名​​​​​​​称​​​​​​​。​​​​​​​该​​​​​​​名​​​​​​​称​​​​​​​必​​​​​​​须​​​​​​​与​​​​​​​群​​​​​​​集​​​​​​​中​​​​​​​的​​​​​​​所​​​​​​​有​​​​​​​ lock_dlm 文​​​​​​​件​​​​​​​系​​​​​​​统​​​​​​​以​​​​​​​及​​​​​​​每​​​​​​​个​​​​​​​本​​​​​​​地​​​​​​​节​​​​​​​点​​​​​​​中​​​​​​​的​​​​​​​所​​​​​​​有​​​​​​​文​​​​​​​件​​​​​​​系​​​​​​​统​​​​​​​(lock_dlm 和​​​​​​​ lock_nolock)不​​​​​​​同​​​​​​​。​​​​​​​以​​​​​​​参​​​​​​​数​​​​​​​变​​​​​​​量​​​​​​​的​​​​​​​格​​​​​​​式​​​​​​​要​​​​​​​求​​​​​​​每​​​​​​​个​​​​​​​文​​​​​​​件​​​​​​​系​​​​​​​统​​​​​​​名​​​​​​​称​​​​​​​。​​​​​​​例​​​​​​​如​​​​​​​:在​​​​​​​本​​​​​​​书​​​​​​​的​​​​​​​一​​​​​​​些​​​​​​​示​​​​​​​例​​​​​​​步​​​​​​​骤​​​​​​​中​​​​​​​使​​​​​​​用​​​​​​​文​​​​​​​件​​​​​​​系​​​​​​​统​​​​​​​名​​​​​​​称​​​​​​​ mydata1 和​​​​​​​ mydata2。​​​​​​​
日​​​​​​​志​​​​​​​
Determine the number of journals for your GFS2 file systems. One journal is required for each node that mounts a GFS2 file system. GFS2 allows you to add journals dynamically at a later point as additional servers mount a filesystem. For information on adding journals to a GFS2 file system, see 第 3.6 节 “在​​​​​​​文​​​​​​​件​​​​​​​系​​​​​​​统​​​​​​​中​​​​​​​添​​​​​​​加​​​​​​​日​​​​​​​志​​​​​​​”.
GNBD 服​​​​​​​务​​​​​​​器​​​​​​​节​​​​​​​点​​​​​​​
如​​​​​​​果​​​​​​​您​​​​​​​正​​​​​​​在​​​​​​​使​​​​​​​用​​​​​​​ GNBD,就​​​​​​​要​​​​​​​确​​​​​​​定​​​​​​​您​​​​​​​需​​​​​​​要​​​​​​​多​​​​​​​少​​​​​​​个​​​​​​​ GNBD 服​​​​​​​务​​​​​​​器​​​​​​​节​​​​​​​点​​​​​​​。​​​​​​​请​​​​​​​注​​​​​​​意​​​​​​​每​​​​​​​个​​​​​​​用​​​​​​​来​​​​​​​设​​​​​​​定​​​​​​​ GNBD 客​​​​​​​户​​​​​​​端​​​​​​​的​​​​​​​ GNBD 服​​​​​​​务​​​​​​​器​​​​​​​的​​​​​​​主​​​​​​​机​​​​​​​名​​​​​​​和​​​​​​​ IP 地​​​​​​​址​​​​​​​。​​​​​​​有​​​​​​​关​​​​​​​使​​​​​​​用​​​​​​​带​​​​​​​ GFS2 的​​​​​​​ GNBD 的​​​​​​​详​​​​​​​情​​​​​​​请​​​​​​​参​​​​​​​考​​​​​​​《​​​​​​​使​​​​​​​用​​​​​​​带​​​​​​​全​​​​​​​局​​​​​​​文​​​​​​​件​​​​​​​系​​​​​​​统​​​​​​​的​​​​​​​ GNBD》​​​​​​​文​​​​​​​档​​​​​​​。​​​​​​​
存​​​​​​​储​​​​​​​设​​​​​​​备​​​​​​​和​​​​​​​分​​​​​​​区​​​​​​​
确​​​​​​​定​​​​​​​用​​​​​​​于​​​​​​​在​​​​​​​文​​​​​​​件​​​​​​​系​​​​​​​统​​​​​​​中​​​​​​​创​​​​​​​建​​​​​​​逻​​​​​​​辑​​​​​​​卷​​​​​​​(使​​​​​​​用​​​​​​​ CLVM)的​​​​​​​存​​​​​​​储​​​​​​​设​​​​​​​备​​​​​​​和​​​​​​​分​​​​​​​区​​​​​​​。​​​​​​​

注意

当​​​​​​​同​​​​​​​时​​​​​​​在​​​​​​​同​​​​​​​一​​​​​​​个​​​​​​​目​​​​​​​录​​​​​​​中​​​​​​​进​​​​​​​行​​​​​​​多​​​​​​​个​​​​​​​生​​​​​​​成​​​​​​​和​​​​​​​删​​​​​​​除​​​​​​​操​​​​​​​作​​​​​​​时​​​​​​​,您​​​​​​​可​​​​​​​能​​​​​​​会​​​​​​​看​​​​​​​到​​​​​​​ GFS2 的​​​​​​​性​​​​​​​能​​​​​​​下​​​​​​​降​​​​​​​。​​​​​​​如​​​​​​​果​​​​​​​这​​​​​​​导​​​​​​​致​​​​​​​您​​​​​​​系​​​​​​​统​​​​​​​性​​​​​​​能​​​​​​​出​​​​​​​现​​​​​​​问​​​​​​​题​​​​​​​,您​​​​​​​应​​​​​​​该​​​​​​​尽​​​​​​​量​​​​​​​将​​​​​​​某​​​​​​​个​​​​​​​节​​​​​​​点​​​​​​​中​​​​​​​的​​​​​​​文​​​​​​​件​​​​​​​生​​​​​​​成​​​​​​​和​​​​​​​删​​​​​​​除​​​​​​​定​​​​​​​位​​​​​​​到​​​​​​​特​​​​​​​定​​​​​​​目​​​​​​​录​​​​​​​。​​​​​​​
Red Hat logoGithubRedditYoutubeTwitter

学习

尝试、购买和销售

社区

关于红帽文档

通过我们的产品和服务,以及可以信赖的内容,帮助红帽用户创新并实现他们的目标。

让开源更具包容性

红帽致力于替换我们的代码、文档和 Web 属性中存在问题的语言。欲了解更多详情,请参阅红帽博客.

關於紅帽

我们提供强化的解决方案,使企业能够更轻松地跨平台和环境(从核心数据中心到网络边缘)工作。

© 2024 Red Hat, Inc.