使用GPFSpagepool 可以缓存用户数据和文件系统元数据。
Use GPFS pagepool to cache user data and file system metadata.
多亏了日志，数百G的文件系统元数据几乎能在瞬间恢复到一致性的状态。
Thanks to the journal, hundreds of Gigabytes of filesystem meta-data can be brought to a consistent state almost instantaneously.
SparcSolaris7的第一个 64位版本增加了文件系统元数据日志记录支持。
The first 64-bit version of Sparc Solaris 7 would add support for file system metadata logging.
Pylesystem：类似于Spotlight或Beagle的实时文件系统元数据索引程序。
Pylesystem: a realtime filesystem metadata indexer similar to Spotlight or beagle.
因为从未给这些文件分配任何块，所以，也就不必释放任何块，甚至根本没有触及底层文件系统元数据。
Since no blocks are ever allocated, there's no need to deallocate any blocks, and the underlying filesystem metadata doesn't even get touched.
使用 仅元数据日志记录，您的文件系统元数据将会异常稳固，因而可能永远不需要执行彻底 fsck。
With metadata-only journaling, your filesystem metadata is going to be rock solid, and you will probably never need to perform an exhaustive fsck.
一旦系统发生崩溃，日志文件就会起到一个检查点的作用，用于恢复未保存的信息，防止损坏文件系统元数据。
If a crash occurs, the journal can be used as a checkpoint to recover unsaved information and avoid corrupting file system metadata.
ext4以多种方式现实了强大的伸缩性，它的伸缩性超越了ext3，并且在文件系统元数据管理方面开辟了新领域。
Ext4 accomplishes this in a number of ways, going beyond ext3 limits and breaking new ground in areas of file system metadata management.
文件系统是对一个存储设备上的数据和元数据进行组织的机制。
A file system is an organization of data and metadata on a storage device.
最后，安装更多内存让文件系统可以把文件和元数据缓存在内存中。
Finally, having extra memory on hand allows the file systems to cache files and metadata in memory.
本例中，gpfs会复制GPFS文件系统中的数据或元数据。
This example has GPFS replicate the data and metadata on the GPFS file system.
在创建GPFS文件系统时，应该先将数据和元数据的副本数量指定为2。
When you created the GPFS file system, you should have specified the number of copies of data and metadata as two.
元数据服务器(cmds)的工作就是管理文件系统的名称空间。
The job of the metadata server (CMDS) is to manage the file system's namespace.
插件元数据驻留在文件系统的.metadata/.plugins目录（相对于工作空间root）下。
Plug-in metadata resides on the file system under the .metadata/.plugins directory, relative to the workspace root.
要注意的是，Ceph客户，对象存储端点，元数据服务器(根据文件系统的容量)可以有许多，而且至少有一对冗余的监视器。
Note that there can be many Ceph clients, many object storage endpoints, numerous metadata servers (depending on the capacity of the file system), and at least a redundant pair of monitors.
inode包含管理文件系统中的对象所需的所有元数据(包括可以在对象上执行的操作)。
The inode contains all the metadata to manage objects in the file system (including the operations that are possible on it).
在这场景中，内容存储库包括两个部分：一个文件系统，单独的文章就是作为片段在此部署的，以及一个数据库，在此部署每一个内容块的元数据。
In this scenario the content repository consists of two parts: a file system, where individual articles are deployed as fragments, and a database, where metadata for each piece of content is deployed.
在对元数据做任何改变以前，文件系统驱动程序会向日志中写入一个条目，这个条目描述了它将要做些什么。
Before the filesystem driver makes any changes to the meta-data, it writes an entry to the journal that describes what it's about to do.
这个网格文件系统不仅需要存储区块，还要存储元数据信息，像目录、文件名、文件大小、最后修改时间等。
The grid file system needs to not only store chunks, but also metadata information, such as directories, files, file sizes, last modification times and so on.
部署脚本需要以这种方式进行编写：如果在文件系统中存在相应的文件的话，就只将元数据写入数据库中。
The deployment scripts need to be written in such a way that metadata is only written to the database if the corresponding file exists on the file system.
然而，为了使得文件系统驱动程序正常工作，有一个很重要的必要条件；它需要在某种合理的、一致的和没有干扰的状态下找到元数据。
However, in order for the filesystem driver to work properly, it has one important requirement; it expects to find the meta-data in some kind of reasonable, consistent, non-corrupted state.
文件系统驱动程序更新适当的元数据，但是没有时间将其缓存中的数据刷新到磁盘的新块中。
The filesystem driver updated the appropriate metadata, but didn't have time to flush the data from its caches to the new blocks on disk.
某些存储库(如许多文件系统)会呈现相反的情况；原始内容会被存储，但是除了文件名以外几乎无法得到元数据。
Some repositories, such as many file systems, will present the opposite case; native content is stored, but very little metadata is available beyond a filename.
就是这个元数据的结构为文件系统提供了其特定的身份和性能特征。
It is the structure of this meta-data that gives a filesystem its particular identity and performance characteristics.
这通过降低在文件系统处于繁忙使用期间元数据日志将“填满”的可能性而改善了性能。
This improves performance by making it less likely that your metadata journal will "fill up" during heavy filesystem usage.
这个问题之所以在XFS 1.0中更加频繁的发生，原因在于对某类元数据的更新必须按照其发生的顺序记录到文件系统中。
The problem manifested itself much more often with XFS 1.0 because certain kinds metadata updates were required to be recorded to the filesystem in the order that they occured.
有些人倾向于备份包含队列管理器配置的文件系统，而其他一些人则备份关于配置的元数据。
Some people prefer to back up the filesystem that contains the queue manager configuration, while others prefer to back up the meta-data about the configuration.
否则，文件系统驱动程序就不能理解和操作元数据，那么您也就不能存取文件了。
Otherwise, the filesystem driver won't be able to understand or manipulate the meta-data, and you won't be able to access your files.
总之，日志文件系统就是一种具有故障恢复能力的文件系统，它利用日志来记录尚未提交到文件系统的修改，以防止元数据破坏(请参见图1)。
To sum up, journaling file systems are fault-resilient file systems that use a journal to log changes before they're committed to the file system to avoid metadata corruption (see Figure 1).
此外，这两个文件系统都支持数据重复删除、内部数据保护(类raid保护)、数据和元数据校验和以及其他存储功能(如快照)。
In addition, both file systems support data de-duplication, internal data protection (RAID-like protection), data and metadata checksums, and other storage features (like snapshots).
应用推荐