cockroachdb / cockroachdb/cockroach
storage: log more info on disk full errors
Open
A-storage
C-escalation-improvement
O-support
T-storage
- Dominant language
- Go
- Stars
- 32.5k
- Forks
- 4.1k
- PR merge metrics
- PR metrics pending
Description
On ENOSPC errors, we exit right away with exit code 10.
We should improve this and try to log the filename, perhaps list the contents of the directory.
This would help especially when ENOSPC comes from the secondary WAL location.
Jira issue: CRDB-66526
Contributor guide
Research direction
No file or test is named. Start by locating the Go ENOSPC handling that exits with code 10, then trace the path for failures from the secondary WAL location. Done means disk-full errors log the filename and, where appropriate, directory contents before exiting.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100