You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Found while looking into a roachtest failure, this is gce specific, I haven't investigated aws. These files are huge and taking most of the root partition, which then causes cascading badness. I think /mnt/data1 is basically the only place they could go:
One of these files was 8.5G on a 9.7G root partition.
ls -l -h /tmp/cores/core.cockroach.3494.dan-1552335208-cdc-ledger-rangefeed-true-0001.1552335817
-rw------- 1 dan dan 8.5G Mar 11 20:28 /tmp/cores/core.cockroach.3494.dan-1552335208-cdc-ledger-rangefeed-true-0001.1552335817
36338: roachprod: change the location cores are written to r=danhhz a=petermattis
/tmp is only 10GB in size, while /mnt/data1 is 370GB.
Fixes#35621
Release note: None
Co-authored-by: Peter Mattis <[email protected]>
Found while looking into a roachtest failure, this is gce specific, I haven't investigated aws. These files are huge and taking most of the root partition, which then causes cascading badness. I think /mnt/data1 is basically the only place they could go:
The text was updated successfully, but these errors were encountered: