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
erikgrinaker opened this issue
Jul 3, 2023
· 2 comments
Labels
A-testingTesting tools and infrastructureC-bugCode not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior.T-testengTestEng Team
In disk-stalled/dmsetup and other tests (see e.g. #106013), we see that a test with UseLocalSSD: false still gets a VM with a local SSD on AWS, and this local SSD is RAID0'ed together with the EBS volume that the test did request. This is related to #98783.
When UseLocalSSD: false, the VM should not use a local SSD at all.
To reproduce:
$ roachtest run --cloud aws --debug-always disk-stalled/dmsetup
[...]
(cluster.go:2247).Run: output in run_094944.124037951_n1-10_echo-0-sudo-blockdev: echo "0 $(sudo blockdev --getsz /dev/nvme1n1) linear /dev/nvme1n1 0" | sudo dmsetup create data1 returned: COMMAND_PROBLEM: exit status 1
[...]
device-mapper: reload ioctl on data1 failed: Device or resource busy
Relevant log entries (from 1.journalctl.txt), note the c6id.xlarge machine type:
A-testingTesting tools and infrastructureC-bugCode not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior.T-testengTestEng Team
In
disk-stalled/dmsetup
and other tests (see e.g. #106013), we see that a test withUseLocalSSD: false
still gets a VM with a local SSD on AWS, and this local SSD is RAID0'ed together with the EBS volume that the test did request. This is related to #98783.When
UseLocalSSD: false
, the VM should not use a local SSD at all.To reproduce:
Relevant log entries (from
1.journalctl.txt
), note thec6id.xlarge
machine type:Jira issue: CRDB-29374
The text was updated successfully, but these errors were encountered: