-
Notifications
You must be signed in to change notification settings - Fork 3.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
roachtest: disk-stalled/fuse/log=false,data=false failed #99215
Comments
No disk stall should've been induced on n1 because this is the log=false, data=false variant. However, n1 experienced a disk stall
Inadvertent disk stalls is also similar to #98202. |
I'm suspicious that there's a bug somewhere in the vfs.FS stack. The disk stall was detected during a syncdata of a WAL file: We do see one goroutine waiting on a
Did the WAL's |
The only
|
We have an automatic goroutine dump from 12:35:42, ~7 seconds before the fatal. We see the same compaction sstable
and a LogWriter goroutine stuck in SyncData:
It looks like the LogWriter's syncdata got unwedged by the time the fatal's goroutine dump? Or somehow it missed it. Either way the earlier goroutine dump seems to indicate this was a legitimate disk stall. |
cc #97968 for tracking |
roachtest.disk-stalled/fuse/log=false,data=false failed with artifacts on release-23.1 @ 80c4895c566a7eaa6f16c4098980509dd3795ad7:
Parameters:
ROACHTEST_cloud=gce
,ROACHTEST_cpu=4
,ROACHTEST_encrypted=false
,ROACHTEST_fs=ext4
,ROACHTEST_localSSD=true
,ROACHTEST_ssd=0
Help
See: roachtest README
See: How To Investigate (internal)
This test on roachdash | Improve this report!
Jira issue: CRDB-25764
The text was updated successfully, but these errors were encountered: