roachtest: failover/chaos/read-write failed

[cockroach-teamcity]

roachtest.failover/chaos/read-write failed with artifacts on release-24.1 @ f876d25ca2dce15331ddc038b3d37dda2eef454a:

(disk_stall.go:475).Setup: full command output in run_134945.177304213_n1-10_echo-0-sudo-blockdev.log: COMMAND_PROBLEM: exit status 1
(cluster.go:2349).Run: context canceled
(cluster.go:2349).Run: context canceled
(cluster.go:2349).Run: context canceled
test artifacts and logs in: /artifacts/failover/chaos/read-write/run_1

Parameters:

• ROACHTEST_arch=amd64
• ROACHTEST_cloud=gce
• ROACHTEST_coverageBuild=false
• ROACHTEST_cpu=2
• ROACHTEST_encrypted=false
• 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/kv-triage

This test on roachdash | Improve this report!

Jira issue: CRDB-38431

[arulajmani]

Failed with:

  | Wraps: (3) Node 9. Command with error:
  |   | ```
  |   | echo "0 $(sudo blockdev --getsz /dev/sdb) linear /dev/sdb 0" | sudo dmsetup create data1
  |   | ```
  |   | device-mapper: reload ioctl on data1 (253:0) failed: Device or resource busy
  |   | Command failed.

@itsbilal does #123506 need to be backported to 24.1?

[arulajmani]

Backported #123782, so this can be closed.