Console

1. In the Google Cloud console, go to theDisks page.

   Go to Disks

2. In the list of disks in your project, click the name of theHyperdisk volume you want to modify.

3. On the disk details page, clickeditEdit.

4. In theAccess mode field, select the access mode that you want:

   • To enable read-only mode, selectMultiple VMs read only.
   • To enable multi-writer mode, selectMultiple VMs read-write
   • (Default) To enable single-writer mode, selectSingle VM read-write.

5. To apply your changes, clickSave.

gcloud

Run thedisks update commandand specify the access mode with the--access-mode flag.

gcloud compute disks updateDISK_NAME  \   --access-mode=DISK_ACCESS_MODE

Replace the following:

• DISK_NAME: the name of theHyperdisk volume that you are modifying.
• DISK_ACCESS_MODE: how VMs can access the data on the disk.Supported values are:
  • READ_ONLY_MANY, for read-only access from multiple VMs.
  • READ_WRITE_MANY, for read-write access from multiple VMs.
  • (Default)READ_WRITE_SINGLE, for read-write access from one VM.

REST

Construct aPATCH request to thecompute.disks.update method.In the request body, set the access mode with the"accessMode" parameter.

PATCH https://compute.googleapis.com/compute/v1/projects/PROJECT_ID/zones/ZONE/disks/DISK_NAME/update{   "accessMode": "DISK_ACCESS_MODE"}

Replace the following:

• PROJECT_ID: your project ID.
• ZONE: the zone where yourHyperdisk volume is located.
• DISK_NAME: the name of theHyperdisk volume to modify.
• DISK_ACCESS_MODE: how VMs can access the data on the disk.Supported values are:
  • READ_ONLY_MANY, for read-only access from multiple VMs.
  • READ_WRITE_MANY, for read-write access from multiple VMs.
  • READ_WRITE_SINGLE, for read-write access from one VM.

Console

1. In the Google Cloud console, go to theDisks page.

   Go to Disks

2. In the list of disks in your project, click the name of theHyperdisk volume for which you want to change the capacityor provisioned performance.

3. On the disk details page, clickEdit.

   1. In theSize field, enter the new size for your disk. The disk sizemust be in the range ofsupported values.
   2. For Hyperdisk Extreme, Hyperdisk Balanced, and Hyperdisk Balanced High Availability:In theProvisioned IOPS field, enter the new IOPS value for yourvolume.
   3. For Hyperdisk Throughput, Hyperdisk ML, Hyperdisk Balanced, and Hyperdisk Balanced High Availability: In theProvisioned throughput field, enter the new throughput valuefor your volume.

4. ClickSave to apply your changes to the disk.

gcloud

Use thedisks update commandand specify the--size,--provisioned-iops, or--provisioned-throughput flags.

To change the size of a Hyperdisk Balanced High Availability volume, include the--region flag.

gcloud compute disks updateDISK_NAME  \    --size=DISK_SIZE  \    [--region=REGION]  \    --provisioned-iops=IOPS_LIMIT  \    --provisioned-throughput=THROUGHPUT_LIMIT

Replace the following:

• DISK_NAME: the name of theHyperdisk volume that you are modifying.
• DISK_SIZE: Optional: The new size of thedisk. The value must be a whole number followed by a size unit of GB forgibibyte, or TB for tebibyte. The disksize must be in the range ofsupported values.
• REGION: Optional. The region where the Hyperdisk Balanced High Availabilitydisk is located
• IOPS_LIMIT: Optional: The IOPSconfiguration for Hyperdisk Extreme, Hyperdisk Balanced, and Hyperdisk Balanced High Availabilityvolumes. The value must be in the range of supported values.
• THROUGHPUT_LIMIT: Optional: The throughputconfiguration for the Hyperdisk Throughput, Hyperdisk ML, Hyperdisk Balanced, or Hyperdisk Balanced High Availability volume,specified as an integer that represents the throughput measured in MiBper second. The value must be in the range of supported values.

REST

Construct aPATCH request to thecompute.disks.update method.In the request body, specify thesizeGb,provisionedIops orprovisionedThroughput parameters.

PATCH https://compute.googleapis.com/compute/v1/projects/PROJECT_ID/zones/ZONE/disks/DISK_NAME{   "sizeGb": "DISK_SIZE,   "provisionedIops": "IOPS_LIMIT",   "provisionedThroughput": "THROUGHPUT_LIMIT"}

To modify a Hyperdisk Balanced High Availability volume, construct aPATCH request to thecompute.regionDisks.update method.

PATCH https://compute.googleapis.com/compute/v1/projects/PROJECT_ID/regions/REGION/disks/DISK_NAME{   "sizeGb": "DISK_SIZE,   "provisionedIops": "IOPS_LIMIT",   "provisionedThroughput": "THROUGHPUT_LIMIT"}

Replace the following:

• PROJECT_ID: your project ID.
• ZONE: the zone where yourHyperdisk volume is located.
• REGION: For Hyperdisk Balanced High Availability disks, this is theregion where the disk is located.
• DISK_NAME: the name of theHyperdisk volume to modify.
• DISK_SIZE: Optional: The new size of thedisk. The value must be a whole number followed by a size unit of GB forgibibyte, or TB for tebibyte. The disksize must be in the range ofsupported values.
• IOPS_LIMIT: Optional: The IOPS configurationfor the Hyperdisk Extreme, Hyperdisk Balanced, or Hyperdisk Balanced High Availability volume. The value must be in therange of supported values.
• THROUGHPUT_LIMIT: Optional: The throughputconfiguration for the Hyperdisk Balanced, Hyperdisk ML, Hyperdisk Balanced, or Hyperdisk Balanced High Availability volume,specified as an integer that represents the throughput measured in MiBper second. The value must be in the range of supported values.

Linux VMs

1. In the Google Cloud console, go to theVM instances page.

   Go to VM instances

2. Click theSSH button next to the instance that has the new diskattached. The browser opens a terminal connection to the instance.

3. Use thedf and thelsblk commands to list the size of the file systemand to find the device names for your disks.

   $sudo df -ThFilesystem      Type      Size  Used Avail Use% Mounted onudev            devtmpfs  3.9G     0  3.9G   0% /dev/dev/nvme0n1p1  ext4      9.7G  2.0G  7.2G  22% //dev/nvme0n1p15 vfat      124M   12M  113M  10% /boot/efi/dev/nvme0n2    ext4       98G   24K   98G   1% /mnt/disks/data

   $sudo lsblkNAME    MAJ:MIN RM  SIZE RO TYPE MOUNTPOINTnvme0n1      259:0    0   20G  0 disk├─nvme0n1p1  259:5    0  9.9G  0 part /├─nvme0n1p14 259:6    0    3M  0 part└─nvme0n1p15 259:7    0  124M  0 part /boot/efinvme0n2      259:4    0  100G  0 disk /mnt/disks/data

   This example includes the following disks:

   • Boot disk: The/dev/nvme0n1p1 partition is on a boot disk thathas been resized to 20 GB. The partition table and the file systemprovide only 9.9 GB to the operating system.
   • Non-boot data disk: The/dev/nvme0n2 non-boot data disk has nopartition table, but the file system on that disk provides 100 GBto the operating system. The mount directory for this disk is/mnt/disks/data.

   Make note of theType column in thedf command output, whichindicates if your disk uses anext4 orxfs file system.

4. Verify the partition type:

   sudo parted -l

   The first time you run this command after resizing a disk, you might seea message similar to the following:

   Warning: Not all of the space available to /dev/nvme0n1 appears to beused, you can fix the GPT to use all of the space (an extra 20971520blocks) or continue with the current setting?Fix/Ignore?

   If you enterFix, the OS will automatically repartition the disk tomake the additional space available to the OS. Skip ahead to the laststep if you don't have any additional disks to modify.

5. If you choose not to use the automatic fix option, or it isn't available,view the information for the disk you want to repartition:

   sudo parted -l /dev/DEVICE_NAME

   Look for field:Partition Table, if the value ismsdos then thedisk has an MBR partition type. This means the maximum size of such diskwould be 2 TB.

6. For a boot disk, resize the root partition and file system on the disk.This example assumes the VM image does not support automatic rootpartitioning and file system resizing.

   1. Resize the root partition by usingparted. For example, thefollowing commands expand partition 1 of the deviceto the maximum possible size:

      1. Openparted on the device:

         sudo parted /dev/DEVICE_NAME

      2. At the prompt, enter:

         (parted)resizepart

      3. At thePartition number? prompt, enter:

         1

      4. At theWarning: Partition /dev/DEVICE_NAMEp1 is beingused. Are you sure you want to continue? prompt, enter:

         Yes

      5. At theEnd? prompt, enter

         100%

      6. At the(parted) prompt, enter:

         (parted)quit

   2. View the new partition table usingparted -l.

      sudo parted -l /dev/DEVICE_NAMEModel: nvme_card-pd (nvme)Disk /dev/DEVICE_NAME: 21.5GBSector size (logical/physical): 512B/512BPartition Table: gptDisk Flags:Number  Start   End     Size    File system  Name  Flags14      1049kB  4194kB  3146kB                     bios_grub15      4194kB  134MB   130MB   fat16              boot, esp1       134MB   21.5GB  21.3GB  ext4

   3. Extend the file system:

      • If you are usingext4, use theresize2fs command:

        sudo resize2fs /dev/DEVICE_NAME

      • If you are usingxfs, use thexfs_growfs command:

        sudo xfs_growfs -d /

      • If you are usingbtrfs,use thebtrfs command:

        sudo btrfs filesystem resize max /

7. For a non-boot data disk, resize the file system on the disk.

   • If you are usingext4, use theresize2fs command to extend thefile system:

     sudo resize2fs /dev/DATA_DEVICE_NAME

     ReplaceDATA_DEVICE_NAME with the device name forthe data disk. In this example, the device name is/dev/nvme0n2.

   • If you are usingxfs, use thexfs_growfs command to extend thefile system:

     sudo xfs_growfsMOUNT_DIR

   • If you are usingbtrfs,use thebtrfs command to extend the file system:

     sudo btrfs filesystem resize maxMOUNT_DIR

     ReplaceMOUNT_DIR with the mount point of the device. Youcan find the mount point listed in theMOUNTPOINT column in theoutput of thelsblk command.

8. Use thedf command to verify that the file system is extended. Forexample:

   df -h /dev/DATA_DEVICE_NAMEFilesystem       Size  Used  Avail    Use%     Mounted on/dev/DATA_DEVICE_NAME   118G  70M   118G     1%MOUNT_DIR

Windows VMs

Use theWindows Disk Management utility to resize partitions on a Windows instance.

1. In the Google Cloud console, go to theVM instances page.

   Go to VM instances

2. Next to the instance that has the resized disk, click theRDP button.The browser opens an RDP connection to the instance.

3. Right-click the Windows Start button and selectDisk Management toopen the Disk Management tool.

   

4. Show the disks partition type by running in Powershell:

   Get-Disk

   under Partition Style column, if the value isMBR then thedisk has an MBR partition type. This means themaximum size of such a disk would be 2 TB.

5. Refresh the Disk Management tool so that it recognizes the additionalspace on your zonal persistent disk. At the top of the Disk Managementwindow, clickAction and selectRefresh.

   

6. On the disk that you resized, right-click the formatted partition andselectExtend Volume.

   

7. Follow the instructions in theExtend Volume Wizard to extend yourexisting partition to include the extra disk space. If the existingpartition is formatted in NTFS, the maximum partition size islimited byits cluster size settings.

8. After you complete the wizard and the volume finishes formatting, checktheStatus column on the list of attached disks to ensure that the newdisk has aHealthy status.