inode 是按目录还是按驱动器限制？
Linux 上的 inode 限制是按子目录还是按整个文件系统？我使用 ububtu 64 位服务器 9.10。
如果是目录限制，是否可以通过将文件拆分到多个子目录来解决 inode 限制？
Are the inode limits on Linux by subdirectory or by the entire file system? I use ububtu 64 bit server 9.10.
Can the inode limit be resolved by splitting files up into multiple sub directories if it's a directory limit?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
索引节点是磁盘文件的 *nix 表示形式。它们由数字标识，而不是由它们在目录结构中所在的路径标识。因此，限制是跨整个文件系统的，无论哪个硬链接（您在目录中看到的文件条目）指向 inode。
Inodes are the *nix representation of disk files. They are identified by a number, not by the path where they are in the directory structure. So the limit is across the whole file system, regardless of which hard link(s) (file entry you see in a directory) point(s) to the inode.
一般来说，两者都有一个限度。我看过 YouTube 上某人的演示视频，他谈到了他们遇到 ext2 上每个目录文件限制的那一天。突然间，没有人可以再上传到 YouTube。他们必须加深目录树。
根据此文档，限制约为 10k-15k 个文件： http:// /www.mjmwired.net/kernel/Documentation/filesystems/ext2.txt
当然，限制取决于您使用的文件系统。例如，我相信 ReiserFS 有更高的限制。
Generally, there is a limit to both. I saw a video of a presentation by someone from YouTube who talked about the day they ran into the per-directory file limit on ext2. Suddenly, nobody could upload to YouTube any more. They had to deepen their directory tree.
According to this doc, the limit is somewhere around 10k-15k files: http://www.mjmwired.net/kernel/Documentation/filesystems/ext2.txt
Of course, the limit depends on what filesystem you are using. I believe ReiserFS has much higher limits, for example.