[[["易于理解","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 instance capacity can be increased or decreased, allowing for adjustments based on usage, and should be monitored to prevent application disruptions.\u003c/p\u003e\n"],["\u003cp\u003eScaling operations do not interrupt read and write operations, but no other instance edits are allowed during this process, and the direction of scaling depends on the tier.\u003c/p\u003e\n"],["\u003cp\u003eBasic HDD and SSD service tiers can only scale up, while other tiers, like Zonal, Regional, and Enterprise, can scale up and down with differing minimum, maximum, and increment values.\u003c/p\u003e\n"],["\u003cp\u003eInode usage is critical because each file consumes one, and if the file system runs out of inodes, no more files can be stored, necessitating an increase in capacity.\u003c/p\u003e\n"],["\u003cp\u003eFilestore instance capacity can be edited via the Google Cloud console's "Edit instance" page or through the \u003ccode\u003egcloud filestore instances update\u003c/code\u003e command, specifying the new file share size.\u003c/p\u003e\n"]]],[],null,["# Scale capacity\n\nThis page shows you how to increase or decrease the capacity of your\nFilestore instances.\n| **Note:** For information about performance scaling, see the [performance documentation](/filestore/docs/performance#performance-scaling).\n\nWhen using Filestore, we recommend that you\n[monitor the utilization of your Filestore instances](/filestore/docs/monitoring-instances)\nso that you can adjust capacity as needed. For example, if you notice that a\nzonal-tier instance with a higher capacity range (previously high scale SSD) no\nlonger needs all of its allocated capacity, you may consider scaling it down.\nSimilarly, if you notice that you are running out of capacity, you may want to\nscale up capacity to prevent your applications from breaking. If the file system\nruns out of inodes, you also need to add capacity. To check the inode usage, run: \n\n df -i\n\nThe command returns something similar to the following: \n\n Filesystem Inodes IUsed IFree IUse% Mounted on\n 10.0.0.2:/vol1 134217728 13 134217715 1% /mnt/test\n\nInode usage\n-----------\n\nEach file stored on the file share consumes one inode. If the file system runs\nout of inodes, you won't be able to store more files on the file share even\nif you haven't reached the maximum allocated capacity. The only way to add\ninodes is by adding capacity. However, reaching the maximum inodes is rare\nand is only a concern if you need to store numerous small files.\n\nFor a better understanding of an instance's available capacity, see\n[Anticipating capacity](/filestore/docs/monitoring-instances#anticpating-capacity).\n\nDifferences in scaling behavior by service tier\n-----------------------------------------------\n\nScaling an instance does not affect its availability and can be performed while\nthe instance is in use. The following table shows how file share capacity can be\nscaled based on the [service tier](/filestore/docs/service-tiers):\n\nScaling the capacity of a zonal tier instance with a higher capacity range can\ntake longer than enterprise and basic tier instances. The actual time required\nvaries depending on the amount of data stored in the instance and the load on the\nFilestore instance. To ensure that your instances don't run out of\ncapacity, perform these operations in advance.\n\nWhen a scaling operation is taking place, you cannot cancel the operation or\nmake any other edits to the instance, but read and write operations are\nuninterrupted. You also cannot scale an enterprise-tier and zonal-tier instance\nto a capacity level that's lower than what's needed for storing its existing\nfile data and metadata. Attempting to do so results in an error.\n\nInstructions for editing an instance\n------------------------------------\n\n### Google Cloud console\n\nTo edit Filestore instances using the Google Cloud console,\nnavigate to the **Edit instance** page, where you can edit the instance\ndescription, manage IP-based access control rules, and scale the file share\nperformance:\n\n1. In the Google Cloud console, go to the Filestore Instances page.\n\n [Go to the Filestore instances page](https://console.cloud.google.com/filestore/instances)\n2. Click the instance ID of the instance you want to edit.\n\n3. On the **Instance details** page, click **Edit** to go to the **Edit\n instance** page.\n\n4. In the **Edit capacity** field, enter the new capacity value.\n\n5. Click **Save**.\n\n### gcloud\n\n#### Before you begin\n\nTo use the gcloud CLI, you must either\n[install the Cloud SDK](/sdk/downloads)\nor use the Cloud Shell\n\nthat's built into the Google Cloud console:\n\n[Go to the Google Cloud console](https://console.cloud.google.com/)\n\n\u003cbr /\u003e\n\n#### `gcloud` command for editing an instance\n\nYou can edit a Filestore instance by running the [`instances\nupdate`](/sdk/gcloud/reference/filestore/instances/update) command. \n\n gcloud filestore instances update \u003cvar translate=\"no\"\u003einstance-id\u003c/var\u003e \\\n --project=\"\u003cvar translate=\"no\"\u003eproject-id\u003c/var\u003e\" \\\n --location=\u003cvar translate=\"no\"\u003elocation\u003c/var\u003e \\\n --file-share=name=\"\u003cvar translate=\"no\"\u003efile-share-name\u003c/var\u003e\",capacity=\u003cvar translate=\"no\"\u003efile-share-size\u003c/var\u003e\n\nwhere:\n\n- \u003cvar translate=\"no\"\u003einstance-id\u003c/var\u003e is the instance ID of the Filestore instance you want to edit.\n- \u003cvar translate=\"no\"\u003eproject-id\u003c/var\u003e is the project ID of the Google Cloud project that\n contains the Filestore instance. You can skip this\n flag if the Filestore instance is in the `gcloud` default\n project. You can set the default project by running:\n\n gcloud config set project \u003cvar translate=\"no\"\u003eproject-id\u003c/var\u003e\n\n- \u003cvar translate=\"no\"\u003elocation\u003c/var\u003e is the location where the Filestore\n instance resides. For enterprise instances, specify a region. For all other\n instances, specify a zone. For example, `us-central1-a`.\n\n Run the `gcloud filestore zones list` command to get a list of supported\n zones. You can skip this flag if the Filestore instance is in\n the `gcloud` default zone. You can set the default zone by running: \n\n gcloud config set filestore/zone \u003cvar translate=\"no\"\u003ezone\u003c/var\u003e\n\n- \u003cvar translate=\"no\"\u003efile-share-name\u003c/var\u003e is the name of the file share that is served\n from the Filestore instance. File share names cannot be changed\n after instance creation.\n\n- \u003cvar translate=\"no\"\u003efile-share-size\u003c/var\u003e is the new size you want for the file share. You\n can specify the file share size in whole numbers using either `GiB` (default)\n or `TiB`. For example, `10TiB`.\n\n To see your available quota, go to the Quotas page in the Google Cloud console:\n\n [Go to the Quotas page](https://console.cloud.google.com/iam-admin/quotas)\n- Optional: For a detailed list of available flags, see the\n [`gcloud filestore instances update`](/sdk/gcloud/reference/filestore/instances/update)\n reference page.\n\nWhat's next\n-----------\n\n- [Known issues](/filestore/docs/known-issues)\n- [Troubleshoot performance-related issues](/filestore/docs/troubleshooting)"]]
