• 7

A PHP Error was encountered

Severity: Notice

Message: Undefined index: userid

Filename: views/question.php

Line Number: 191


File: /home/prodcxja/public_html/questions/application/views/question.php
Line: 191
Function: _error_handler

File: /home/prodcxja/public_html/questions/application/controllers/Questions.php
Line: 433
Function: view

File: /home/prodcxja/public_html/questions/index.php
Line: 315
Function: require_once

I keep on running out of disk space while trying to compile gcc and I keep on creating larger and larger disk sizes and after 5 hours of compiling, it runs out of disk space. I've resized the disk 4 times now, restarted the compile step for the 4th time now with a 500GB disk.

When I ran df -h to see how much space was used, it only says 9.7GB, but that's considered 100%.

enter image description here

enter image description here

enter image description here

I thought there might be another disk, but I'm only seeing sda and its partition

ls /dev/sd*
/dev/sda  /dev/sda1

So is my disk actually 500GB in size and df is just reporting it wrong (in which case compiling gcc chows up the whole 500GB) or is Google Cloud's Dashboard reporting it wrong, df reporting it right and compiling gcc is not chowing through 500GB ?

Either way, unless I'm supposed to do something to make use of the 500GB (which is counter-intuitive by the way), I'm guessing this is a bug?

(I've searched before I posted, I've only seen AWS related issues)

UPDATE - lsblk explains it:

sda      8:0    0  500G  0 disk 
??sda1   8:1    0   10G  0 part /

It seems Google Compute Engine does offer automatic resizing of root partitions on most operating systems (I'm usually using Debian, so never had such issues), CentOS it seems is not one of them.


In my case, manual repartition is needed, see:

After going through the steps, my disk size is now 500GB

sda      8:0    0  500G  0 disk 
??sda1   8:1    0  500G  0 part /
  • 11
Reply Report
      • 1
    • I'd recommend taking a snapshot of your VM if GCE allows for that before you give that a try. And if you've not done this before, I'd definitely recommend trying it on non-Production instances before doing this in Production.
      • 1
    • Hehe, too late, already wrecked the machine. Luckily made a snapshot last night, so no major damage.

Here are the steps in you have single xfs (/dev/sda1) partition.

Don`t forget to make snapshot before trying!

First re-create your root partition, type this command:

(echo d; echo n; echo p; echo 1; echo ; echo; echo w) | sudo fdisk /dev/sda

Then restart your server. Once restarted, grow your partition

xfs_growfs /dev/sda1

Verify with:

df -h
  • 4
Reply Report

Warm tip !!!

This article is reproduced from Stack Exchange / Stack Overflow, please click

Trending Tags