Database Disk Almost Full

Database Disk Almost Full

Buy time safely, never delete the wrong files, then find what grew

What you'll learn

  • Why a full disk can stop a database
  • Buying time safely, and what never to delete
  • Finding what grew, including a stuck write-ahead log
  • Alerting on growth rate instead of a late threshold

In this video, we'll look at what to do when you get a 2 AM alert that your database disk is 95% full and still climbing. We'll cover why writes start failing when the disk fills up, how to buy time by making the disk bigger, and why you should never delete files you don't recognize.

We'll also look at how to find what grew, including a write-ahead log that keeps growing because a replica or tool stopped reading it, old logs, and temporary files, and how to fix each one.

By the end, you'll know how to handle a filling disk and set up alerts that warn you days before it's full.

More videos

32 short explainers so far, with more on the way

View all videos

Join the Community

roadmap.sh is among the top 10 most starred projects on GitHub and is visited by hundreds of thousands of developers every month.

Top 10 out of 28M!

371K

GitHub Stars

Star us on GitHub
Help us reach #1

+90kevery month

+3.2M

Registered Users

Register yourself
Commit to your growth

+2kevery month

52K

Discord Members

Join on Discord
Join the community

RoadmapsGuidesFAQsYouTube

roadmap.shby@nilbuild

Community created roadmaps, best practices, projects, articles, resources and journeys to help you choose your path and grow in your career.

© roadmap.sh·Terms·Privacy·

ThewNewStack

The top DevOps resource for Kubernetes, cloud-native computing, and large-scale development and deployment.