[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["很难理解","hardToUnderstand","thumb-down"],["信息或示例代码不正确","incorrectInformationOrSampleCode","thumb-down"],["没有我需要的信息/示例","missingTheInformationSamplesINeed","thumb-down"],["翻译问题","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["最后更新时间 (UTC):2025-08-18。"],[[["\u003cp\u003eFilestore instances can encounter capacity issues related to inode usage, where each file consumes one inode, and if \u003ccode\u003eIUse%\u003c/code\u003e reaches 100%, no more files can be stored, even if storage capacity remains.\u003c/p\u003e\n"],["\u003cp\u003eThe \u003ccode\u003edf\u003c/code\u003e command differs from the \u003ccode\u003edu\u003c/code\u003e command in reporting free disk space because \u003ccode\u003edf\u003c/code\u003e accounts for space used by deleted but still-open files, while \u003ccode\u003edu\u003c/code\u003e does not, which means \u003ccode\u003edu\u003c/code\u003e might report a higher amount of free space.\u003c/p\u003e\n"],["\u003cp\u003eYou can identify deleted files that are still being used by a process by running the \u003ccode\u003elsof | grep deleted\u003c/code\u003e command, which will help you understand why disk space may not be freeing up.\u003c/p\u003e\n"],["\u003cp\u003eYou can use Configurable performance to control the number of client connections with IOPS, instead of the provisioned instance capacity.\u003c/p\u003e\n"]]],[],null,["# Troubleshoot capacity issues\n\nThe following sections describe scenarios where an instance might encounter\ncapacity issues and provides steps to help address the problem.\n\n\"No space left on device\"\n-------------------------\n\nCheck if the Filestore instance has sufficient inodes by running\nthe following command on the client VM: \n\n df -i\n\nThe command returns something similar to the following: \n\n```\nFilesystem Inodes IUsed IFree IUse% Mounted on\n10.0.0.2:/vol1 134217728 13 134217715 1% /mnt/test\n```\n\nEach file stored on the file share consumes one inode. If `IUse%` reaches 100%,\nyou are not able to store more files on the file share even if you haven't\nreached the maximum allocated capacity. The number of inodes scales with\ncapacity. If you want to add more inodes, you must add more capacity. However,\nreaching the maximum number of inodes is rare and is only a concern if you need\nto store numerous small files.\n\nFor more information, see [Inode usage](/filestore/docs/scale#inode-usage) and\n[Monitoring instances](/filestore/docs/monitoring-instances#anticipating-capacity).\n\n`df` and `du` commands report different amounts of free disk space\n------------------------------------------------------------------\n\nWhen a file that is open by a running process is deleted, the disk space that\nthe file consumes does not get freed until the file is closed. The `df` commands\naccounts for the space consumed by deleted open files, whereas the `du` command\ndoes not. This difference in calculation is why the `du` command often shows\nmore free space than `df`.\n\nTo display the deleted files that are still open by a running process, run: \n\n lsof | grep deleted\n\nNumber of client connections\n----------------------------\n\nYou can control the number of client connections with IOPS rather than\nprovisioned instance capacity by using\n[Configurable performance](/filestore/docs/getting-support) (Allowllisted GA).\n\nFor more information, see [About configurable performance](/filestore/docs/getting-support)\nand [Client connection limits](/filestore/docs/limits#number_of_clients)."]]