roachtest: disk-stalled/detection/cgroup/write-only/logs-too=true failed

[cockroach-teamcity]

roachtest.disk-stalled/detection/cgroup/write-only/logs-too=true failed with artifacts on master @ ff52bbf0c5fcc807828c6fa5aeeb1d19c24270fc:

(disk_stall.go:536).Stall: full command output in run_125711.580340077_n1_sudo-binbash-c-echo-.log: COMMAND_PROBLEM: exit status 1
(cluster.go:2347).Run: context canceled
test artifacts and logs in: /artifacts/disk-stalled/detection/cgroup/write-only/logs-too=true/cpu_arch=arm64/run_1

Parameters:

• ROACHTEST_arch=arm64
• ROACHTEST_cloud=gce
• ROACHTEST_coverageBuild=false
• ROACHTEST_cpu=4
• ROACHTEST_encrypted=true
• ROACHTEST_fs=ext4
• ROACHTEST_localSSD=false
• ROACHTEST_metamorphicBuild=false
• ROACHTEST_ssd=0

Help

See: roachtest README

See: How To Investigate (internal)

See: Grafana

/cc @cockroachdb/storage

This test on roachdash | Improve this report!

Jira issue: CRDB-37615

[itsbilal]

run_125711.580340077_n1_sudo-binbash-c-echo-: 12:57:11 cluster.go:2368: > sudo /bin/bash -c 'echo 8:16 wbps=4 > /sys/fs/cgroup/system.slice/cockroach-system.service/io.max'
/bin/bash: line 1: echo: write error: No such device

did something change on this node that moved the cgroup controller around, such as the OS version or the cockroach service name?

Either way, not a release blocker, seems test/infra related.

[itsbilal]

Closing as an infra flake due to lack of a recurrence. In my own experience, this happens when we create a gce node with local ssds instead of PD.