ci: clarify runner disk diagnostics
All checks were successful
Deploy to Frontend Servers / deploy (push) Successful in 1m11s

This commit is contained in:
TerryM
2026-06-09 01:14:08 +08:00
parent 41d737da11
commit c882cce0a4
2 changed files with 7 additions and 3 deletions

View File

@@ -16,7 +16,8 @@ jobs:
echo "=== Disk before resize ===" echo "=== Disk before resize ==="
df -h / df -h /
lsblk -o NAME,SIZE,TYPE,MOUNTPOINT,FSTYPE,PKNAME,PARTN || true hostname || true
lsblk -o NAME,SIZE,TYPE,MOUNTPOINT,FSTYPE || true
ROOT_SOURCE=$(findmnt -n -o SOURCE / 2>/dev/null || true) ROOT_SOURCE=$(findmnt -n -o SOURCE / 2>/dev/null || true)
ROOT_FSTYPE=$(findmnt -n -o FSTYPE / 2>/dev/null || true) ROOT_FSTYPE=$(findmnt -n -o FSTYPE / 2>/dev/null || true)
@@ -39,6 +40,9 @@ jobs:
fi fi
echo "Root source: $ROOT_SOURCE ($ROOT_FSTYPE), disk: /dev/${DISK_NAME:-unknown}, partition: ${PART_NUM:-unknown}" echo "Root source: $ROOT_SOURCE ($ROOT_FSTYPE), disk: /dev/${DISK_NAME:-unknown}, partition: ${PART_NUM:-unknown}"
if [ -n "$DISK_NAME" ]; then
echo "Visible disk bytes: $(sudo blockdev --getsize64 "/dev/$DISK_NAME" 2>/dev/null || echo unknown)"
fi
if [ -n "$DISK_NAME" ] && [ -n "$PART_NUM" ]; then if [ -n "$DISK_NAME" ] && [ -n "$PART_NUM" ]; then
if ! command -v growpart >/dev/null 2>&1; then if ! command -v growpart >/dev/null 2>&1; then
sudo dnf -y install cloud-utils-growpart || sudo yum -y install cloud-utils-growpart || true sudo dnf -y install cloud-utils-growpart || sudo yum -y install cloud-utils-growpart || true
@@ -61,7 +65,7 @@ jobs:
echo "Available on root volume: ${AVAIL_MB} MB" echo "Available on root volume: ${AVAIL_MB} MB"
if [ "${AVAIL_MB:-0}" -lt 3500 ]; then if [ "${AVAIL_MB:-0}" -lt 3500 ]; then
echo "::error::Less than 3.5GB free on root volume (${AVAIL_MB}MB)." echo "::error::Less than 3.5GB free on root volume (${AVAIL_MB}MB)."
echo "If EBS is already 200GB, grow the EC2 root partition/filesystem on the runner host or install cloud-utils-growpart." echo "growpart could not find extra space. If AWS says EBS is 200GB, this job is likely running on the wrong runner/volume or the OS still has not seen the expanded disk; reboot/rescan the runner host and verify lsblk shows ~200G for the parent disk."
exit 1 exit 1
fi fi

View File

@@ -59,7 +59,7 @@ sudo resize2fs <root-partition> # ext filesystems
# or sudo xfs_growfs / # xfs filesystems # or sudo xfs_growfs / # xfs filesystems
``` ```
If the step cannot find `growpart`, it tries to install `cloud-utils-growpart` with `dnf`/`yum`. If install is blocked, install it manually on the runner host and rerun the workflow. The step also prints `lsblk`; if the parent disk still shows 8GB there, AWS has not attached/refreshed the expanded EBS volume for this instance. If the step cannot find `growpart`, it tries to install `cloud-utils-growpart` with `dnf`/`yum`. If install is blocked, install it manually on the runner host and rerun the workflow. The step also prints `hostname`, `lsblk`, and the visible parent disk byte size. If `growpart` says `NOCHANGE` and the parent disk still shows 8GB, the job is running on the wrong runner/volume or the OS still has not seen the expanded EBS volume; verify the EC2 instance/volume pair and reboot/rescan the runner host.
### Node version is too old ### Node version is too old