Files within a file system are represented uniquely as inodes.
文件系统中的文件由inode唯一地表示。
Each allocation group allocates inodes as needed, in groups of 64.
每个分配组在需要时以64个索引节点为一组来分配它们。
Exofs maps inodes to the object identifiers (OIDs) in the object system.
exofs将inode映射到对象系统中的对象标识符(OID)。
When this makes some sectors or inodes invalid, you will end up losing valuable data.
当这导致某些扇区或节点无效时，将最终丢失宝贵的数据。
For example, inodes can be allocated with alloc_inode or deleted with destroy_inode.
例如，可以用alloc_inode分配inode，用destroy _ inode删除inode。
This structure defines the set of functions for managing inodes within the file system.
这个结构定义一组用来管理这个文件系统中的inode的函数。
When the file system is scanned at mount time, the valid inodes can be quickly identified.
在挂载期间扫描文件系统时，可以快速标识有效的inode。
Only file system inodes are stored permanently, where dentry objects are used to improve performance.
仅永久储存文件系统inode,dentry对象的目的是改善性能。
The first list defines the inodes that are currently in use; the second list defines the inodes that are unused.
第一个列表定义当前使用的inode；第二个列表定义未使用的 inode。
Hopefully, after reading this article, you understand inodes better, their importance to AIX, and also how to manage them.
希望在阅读完本文之后，您可以更好地了解inode、它们对于AIX系统的重要性，以及如何管理它们。
If you are copying from one file system to another of exactly the same type, the number of inodes used should be identical.
如果您将文件从一个文件系统复制到另一个与其类型完全相同的文件系统，那么所使用的索引节点的数目应该是相等的。
Typically, there is an adequate number of inodes associated with a file system, but running out of inodes is always a possibility.
通常，与一个文件系统相关联的inode的数目足够多，但耗尽inode的可能性始终存在。
Note that because files are used to represent other types of objects, such as devices or memory, inodes are used to represent them also.
注意，因为文件用于表示其他类型的对象(比如设备或内存)，所以也使用inode来表示它们。
Because hard links point to an inode, and inodes are only unique within a particular file system, hard links cannot cross file systems.
由于硬链接指向一个inode，且inode仅在特定文件系统内是惟一的，硬链接不能跨越文件系统。
The number of inodes that can be created in a filesystem is dynamic and it is only limited by the amount of free space in the filesystem.
在文件系统中可以创建的索引节点的数目是动态变化的，并且只受到文件系统中剩余空间的限制。
You will see inodes again later in this article and also in the article Create and change hard and symbolic links (see the series roadmap).
您将在本文后面以及创建和修改硬链接和符号链接(参见学习Linux, 101： LPIC - 1路线图)中再次见到有关inode的介绍。
Rather than restoring the system or even rebuilding the operating system, you can use FSCK to repair file systems or correct damaged inodes.
您可以使用fsck来修复文件系统或者修正受损的inode，而不是还原系统、或者甚至重新构建操作系统。
Another good test, if you are copying file system to file system, is to compare inode Numbers; these show how many inodes have been allocated.
如果您将文件从一个文件系统复制到另一个文件系统，那么还有一种好的测试方法，即比较索引节点数目，这将显示分配了多少个索引节点。
The super_operations structure defines a number of functions for reading and writing inodes as well as higher-level operations (such as remounting).
super_operations结构为读写节点和高级操作(比如重新挂载)定义大量函数。
Furthermore, you do not need to assign inodes anymore when creating file systems, as they are now dynamically allocated by JFS2 (meaning you won't be running out of them).
另外，在创建文件系统的时候不再需要分配索引节点，因为现在它们是由JFS2动态分配的(这意味着将不会耗尽索引节点)。
If for some reason a file system did reach 100 percent of its inodes used, you won't be able to create additional files, devices, directories, and so on in the file system.
如果由于某种原因，某个文件系统inode的使用率达到百分之百，那么您将无法在该文件系统中创建更多的文件、设备、目录等等。
If for some reason a file system did reach 100 percent of its inodes used, you won't be able to create additional files, devices, directories, and so on in the file system.
如果由于某种原因，某个文件系统inode的使用率达到百分之百，那么您将无法在该文件系统中创建更多的文件、设备、目录等等。
应用推荐