Update workflows/operations/Linux/Expanding Linux Filesystems.md
All checks were successful
Automatic Documentation Deployment / Sync Docs to https://kb.bunny-lab.io (push) Successful in 7s

This commit is contained in:
2026-04-10 21:40:47 -06:00
parent 9e566f4c86
commit de4757b0c7

View File

@@ -95,6 +95,14 @@ This step goes over how to increase the usable space of the virtual disk within
**Point of No Return**: **Point of No Return**:
When you press `w` in both cases of `gdisk` or `fdisk`, then ++enter++ the changes will be written to disk, meaning there is no turning back unless you have full GuestVM backups or a snapshot to rollback with, or something like Veeam Backup & Replication. Be certain the first and last sector values are correctly configured before proceeding. (Default values generally are good for this) When you press `w` in both cases of `gdisk` or `fdisk`, then ++enter++ the changes will be written to disk, meaning there is no turning back unless you have full GuestVM backups or a snapshot to rollback with, or something like Veeam Backup & Replication. Be certain the first and last sector values are correctly configured before proceeding. (Default values generally are good for this)
=== "Using GROWPART (Ubuntu)"
``` sh
echo 1 | sudo tee /sys/class/block/sda/device/rescan
growpart /dev/sda 2
sudo resize2fs /dev/sda2 # Assuming ext4 filesystem, if unsure, run "df -Th"
```
## Detect the New Partition Sizes ## Detect the New Partition Sizes
At this point, the operating system wont detect the changes without a reboot, so we are going to force the operating system to detect them immediately with the following commands to avoid a reboot (if we can avoid it). At this point, the operating system wont detect the changes without a reboot, so we are going to force the operating system to detect them immediately with the following commands to avoid a reboot (if we can avoid it).
``` sh ``` sh