roachtest: failover/chaos/read-only/lease=expiration failed

[cockroach-teamcity]

roachtest.failover/chaos/read-only/lease=expiration failed with artifacts on master @ 1382b26a97bf6f70a07d363dc319283c173359eb:

(cluster.go:2281).Run: output in run_131221.762972458_n1-10_echo-0-sudo-blockdev: echo "0 $(sudo blockdev --getsz /dev/sdb) linear /dev/sdb 0" | sudo dmsetup create data1 returned: COMMAND_PROBLEM: exit status 1
(cluster.go:2281).Run: cluster.RunE: context canceled
(cluster.go:2281).Run: cluster.RunE: context canceled
(cluster.go:2281).Run: cluster.RunE: context canceled
test artifacts and logs in: /artifacts/failover/chaos/read-only/lease=expiration/run_1

Parameters: ROACHTEST_arch=amd64 , ROACHTEST_cloud=gce , ROACHTEST_cpu=2 , ROACHTEST_encrypted=false , ROACHTEST_fs=ext4 , ROACHTEST_localSSD=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-30437

[erikgrinaker]

Looks like #108115 didn't help. Something else must be accessing the device then, not sure what that would be. We'll have to add some debug logging to figure out what else is holding onto the device, e.g. via lsof.

[github-actions]

We have marked this test failure issue as stale because it has been
inactive for 1 month. If this failure is still relevant, removing the
stale label or adding a comment will keep it active. Otherwise,
we'll close it in 5 days to keep the test failure queue tidy.

[nvanbenschoten]

Hasn't failed in a month. Artifacts gone. Closing.