-
Notifications
You must be signed in to change notification settings - Fork 153
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CI out of disk space #1578
Comments
There has been an intermittent kokoro failure where the |
dmesg from a failed container. Looks like no partition was found on sdb:
|
Ya. It looks like the disk is there, but just needs to be partitioned and formatted. Huh. Maybe a race condition? |
Sounds like some type of race-condition.... The following debug information could be useful; sudo partprobe -s || true
sudo dmesg | tail -n 30 || true
sudo cat /proc/partitions || true
sudo cat /etc/fstab || true
sudo cat /etc/mtab || true
sudo lsblk --list --output 'NAME,KNAME,FSTYPE,MOUNTPOINT,LABEL,UUID,PARTTYPE,PARTLABEL,PARTUUID' || true
sudo sfdisk --list || true
sudo systemctl | grep mount || true
sudo systemctl | grep dev || true |
Ah, the sdb1 appears after 15 seconds. I think my recently added check is too early.
|
@dnltz -- This is super interesting! We should probably make sure the system waits until |
Another instance of
|
@litghost - Any idea why |
I have made some modifications to the kokoro base image that is used here to hopefully fix the issue. Please keep an eye out for this problem continuing to appear. |
Closing since kokoro is not used anymore. |
The last merge resulted in the Zynq CI to fail due to insufficient disk space (link to CI).
The text was updated successfully, but these errors were encountered: