调整默认的10GB启动驱动器Google Cloud Platform的大小

时间:2014-07-01 06:40:45

标签: google-cloud-platform google-cloud-storage

在Google云端平台上创建实例时,如何增加默认的10GB启动驱动器?我已经阅读了关于此的不同答案,没有什么超级明确的。我是平台的初学者,如果有人能用简单的话告诉我如何做到这一点,我真的很感激。

4 个答案:

答案 0 :(得分:12)

使用以下步骤通过Google Cloud Platform上的CentOS增加启动大小。

ssh into vm instance

[user@user-srv ~]$ df -h
Filesystem            Size  Used Avail Use% Mounted on
/dev/sda1             9.9G  898M  8.5G  10% /
tmpfs                 296M     0  296M   0% /dev/shm
[user@user-srv ~]$ sudo fdisk /dev/sda

The device presents a logical sector size that is smaller than
the physical sector size. Aligning to a physical sector (or optimal
I/O) size boundary is recommended, or performance may be impacted.

WARNING: DOS-compatible mode is deprecated. It's strongly recommended to
        switch off the mode (command 'c') and change display units to
        sectors (command 'u').

Command (m for help): p

Disk /dev/sda: 53.7 GB, 53687091200 bytes
4 heads, 32 sectors/track, 819200 cylinders
Units = cylinders of 128 * 512 = 65536 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x0004a990

  Device Boot      Start         End      Blocks   Id  System
/dev/sda1              17      163825    10483712+  83  Linux

Command (m for help): c
DOS Compatibility flag is not set

Command (m for help): u
Changing display/entry units to sectors

Command (m for help): p

Disk /dev/sda: 53.7 GB, 53687091200 bytes
4 heads, 32 sectors/track, 819200 cylinders, total 104857600 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x0004a990

  Device Boot      Start         End      Blocks   Id  System
/dev/sda1            2048    20969472    10483712+  83  Linux

Command (m for help): p

Disk /dev/sda: 53.7 GB, 53687091200 bytes
4 heads, 32 sectors/track, 819200 cylinders, total 104857600 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x0004a990

  Device Boot      Start         End      Blocks   Id  System
/dev/sda1            2048    20969472    10483712+  83  Linux

Command (m for help): n
Command action
  e   extended
  p   primary partition (1-4)
p
Partition number (1-4): 1
Partition 1 is already defined.  Delete it before re-adding it.

Command (m for help): d
Selected partition 1

Command (m for help): n
Command action
  e   extended
  p   primary partition (1-4)
p
Partition number (1-4): 1
First sector (2048-104857599, default 2048):
Using default value 2048
Last sector, +sectors or +size{K,M,G} (2048-104857599, default 104857599):
Using default value 104857599

Command (m for help): w
The partition table has been altered!

Calling ioctl() to re-read partition table.

WARNING: Re-reading the partition table failed with error 16: Device or resource busy.
The kernel still uses the old table. The new table will be used at
the next reboot or after you run partprobe(8) or kpartx(8)
Syncing disks.
[user@user-srv ~]$ df -h
Filesystem            Size  Used Avail Use% Mounted on
/dev/sda1             9.9G  898M  8.5G  10% /
tmpfs                 296M     0  296M   0% /dev/shm
[user@user-srv ~]$ sudo reboot

Broadcast message from user@user-srv
(/dev/pts/0) at 3:48 ...

The system is going down for reboot NOW!
[user@user-srv ~]$ Connection to 23.251.144.204 closed by remote host.
Connection to 23.251.144.204 closed.

Robetus-Mac:~ tomassiro$ gcutil listinstances --project="project-name"
+-------+---------------+---------+----------------+----------------+
| name  | zone          | status  | network-ip     | external-ip    |
+-------+---------------+---------+----------------+----------------+
| srv-1 | us-central1-a | RUNNING | 10.230.224.112 | 107.168.216.20 |
+-------+---------------+---------+----------------+----------------+

ssh into vm instance

[user@user-srv ~]$ df -h
Filesystem            Size  Used Avail Use% Mounted on
/dev/sda1             9.9G  898M  8.5G  10% /
tmpfs                 296M     0  296M   0% /dev/shm

[user@user-srv ~]$ sudo resize2fs /dev/sda1
resize2fs 1.41.12 (17-May-2010)
Filesystem at /dev/sda1 is mounted on /; on-line resizing required
old desc_blocks = 1, new_desc_blocks = 4
Performing an on-line resize of /dev/sda1 to 13106944 (4k) blocks.
The filesystem on /dev/sda1 is now 13106944 blocks long.

[user@user-srv ~]$ df -h
Filesystem            Size  Used Avail Use% Mounted on
/dev/sda1              50G  908M   46G   2% /
tmpfs                 296M     0  296M   0% /dev/shm
[user@user-srv ~]$ exit
logout
Connection to 23.251.144.204 closed.

答案 1 :(得分:1)

步骤很简单:

  1. 从尺寸较大的现有源图像创建新磁盘
  2. 使用刚创建的磁盘创建新实例(选择现有磁盘)
  3. 系统启动后,使用命令“df -h”,您可以看到存储仍为9.9GB。
  4. 按照https://developers.google.com/compute/docs/disks
  5. 中“重新分区根永久磁盘”部分中的步骤(从步骤4-12开始)
  6. 成品!!

答案 2 :(得分:1)

不重新启动或重新启动会增加GCP云VM或Google云引擎中的启动大小

如果危险超过80%,请检查第一个磁盘使用率是否超过/dev/sda1的{​​{1}}的80%。

无需重新启动即可即时更新VM的磁盘大小

  1. 首先从控制台增加磁盘大小
  2. 虚拟机内部的SSH:sudo growpart /dev/sda 1
  3. 调整文件系统大小:sudo resize2fs /dev/sda1
  4. 验证:df -h

答案 3 :(得分:0)

比直接编辑分区更安全的方法并且不需要维护自己的图像,是dracut的growroot模块&云初始化

我在CentOS 6& 7 Google Compute,AWS&天青。

## you'll need to be root or use sudo
yum -y install epel-release
yum -y install cloud-init cloud-initramfs-tools dracut-modules-growroot cloud-utils-growpart
rpm -qa kernel | sed -e 's/^kernel-//' | xargs -I {} dracut -f /boot/initramfs-{}.img {}
# reboot for the resize to take affect

分区将在下次启动时自动调整大小。

注意:

  • 这是内置于Ubuntu的,这就是为什么你没有看到那里的问题。
  • RedHat& CentOS拥有大多数预先构建的图像,而不仅仅是Google Cloud。这种方法可以在任何地方使用。