You can increase or change the amount of storage available for Git repositories, databases, search indexes, and other persistent application data.
Warning: The process for allocating new system resources will vary by virtualization platform and resource type, but the first step is always to configure monitoring and alerting of key system resources.
As more users join your GitHub Enterprise instance, you may need to resize your storage volume accordingly.
Note: You'll need to place your instance in maintenance mode before resizing the user storage volume.
|Platform||Information on resizing storage|
Based on your seat count, we recommend this hardware configuration:
|Seats||vCPUs||Memory||Attached Storage||Root Storage|
|10-500||2||16 GB||100 GB||80 GB|
|500-3000||4||32 GB||250 GB||80 GB|
|3000-5000||8||64 GB||500 GB||100 GB|
|5000-8000||12||72 GB||750 GB||120 GB|
|8000-10000+||16||128 GB||1000 GB||140 GB|
These are minimum recommendations. More resources may be required depending on your usage, such as user activity and selected integrations.
In order to complete the data storage expansion, you'll need to run the
Use your virtualization platform's tools to allocate additional physical storage to the user volume.
As a site admin, SSH into your GitHub Enterprise instance:
ssh -p 122 admin@hostname
Place the appliance in maintenance mode.
To detect new storage allocation, stop the storage and run the rescan command:
sudo stop ghe-storage echo 1 | sudo tee /sys/class/scsi_device/*/device/rescan
Expand the filesystem to take advantage of the newly allocated space:
Restart the storage.
sudo start ghe-storage