[[["이해하기 쉬움","easyToUnderstand","thumb-up"],["문제가 해결됨","solvedMyProblem","thumb-up"],["기타","otherUp","thumb-up"]],[["이해하기 어려움","hardToUnderstand","thumb-down"],["잘못된 정보 또는 샘플 코드","incorrectInformationOrSampleCode","thumb-down"],["필요한 정보/샘플이 없음","missingTheInformationSamplesINeed","thumb-down"],["번역 문제","translationIssue","thumb-down"],["기타","otherDown","thumb-down"]],["최종 업데이트: 2025-09-04(UTC)"],[],[],null,["# Expand VM disks\n\nYou can increase the size of your virtual machine (VM) disk partition when your\nVM instance requires additional storage space or increased performance limits.\n\nYou can only increase, and not decrease, the size of a disk. To decrease the disk\nsize, you must create a new disk with a smaller size. Until you delete the\noriginal, larger disk, you are charged for both disks.\n\nThis page provides instructions to increase the size of both boot and non-boot\ndisks.\n\nBefore you begin\n----------------\n\nTo get the permissions you need to perform disk expansion, ask your Project IAM\nAdmin to grant you the Project VirtualMachine Admin (`project-vm-admin`) role in\nthe namespace where the VM resides. Follow the steps to\n[verify](/distributed-cloud/hosted/docs/latest/appliance/application/ao-user/vms/preparation#verify-user-access)\nthat you have the required permissions.\n\nDisk expansion\n--------------\n\nFollow the gdcloud or API steps to expand the disk size. \n\n### gdcloud\n\nExpand the VM disk: \n\n gdcloud compute disks resize \u003cvar translate=\"no\"\u003eDISK_NAME\u003c/var\u003e --project=\u003cvar translate=\"no\"\u003ePROJECT\u003c/var\u003e --size=\u003cvar translate=\"no\"\u003eNEW_SIZE\u003c/var\u003e\n\n- Replace \u003cvar translate=\"no\"\u003eDISK_NAME\u003c/var\u003e with the name of the disk.\n\n- Replace \u003cvar translate=\"no\"\u003ePROJECT\u003c/var\u003e with the name of the\n GDC project in which the VM lives.\n\n- Replace \u003cvar translate=\"no\"\u003eNEW_SIZE\u003c/var\u003e with the new size of the disk.\n\n### API\n\n1. Expand the `VirtualMachineDisk` by updating the `.spec.size` field:\n\n kubectl --kubeconfig \u003cvar translate=\"no\"\u003eMANAGEMENT_API_SERVER\u003c/var\u003e \\\n apply -n \u003cvar translate=\"no\"\u003ePROJECT\u003c/var\u003e -f - \u003c\u003cEOF\n apiVersion: virtualmachine.gdc.goog/v1\n kind: VirtualMachineDisk\n metadata:\n name: \u003cvar translate=\"no\"\u003eVM_BOOT_DISK_NAME\u003c/var\u003e\n spec:\n source:\n image:\n name: \u003cvar translate=\"no\"\u003eBOOT_DISK_IMAGE_NAME\u003c/var\u003e\n namespace: vm-system\n size: \u003cvar translate=\"no\"\u003eBOOT_DISK_SIZE\u003c/var\u003e\n EOF\n\n Replace the following variables:\n\n2. Wait until the `.spec.size` field updates to the new size.\n\nExpand the file systems and partitions\n--------------------------------------\n\nAfter expanding the block device, you must expand the guest's partition and file\nsystem so that applications can consume the additional space. Some OS's do this\nautomatically using `cloud-init`."]]