Mounted volume not working???

@daniel.lasek

1.9K followers · usually 476 views a post

Views

2.8K

Likes

53

Comments

4

Shares

2

Selling · SaaS › Other SaaS

DigitalOcean

digitalocean.com ↗

Why it worked

The video addresses a common and frustrating technical problem (disk full errors despite available space) with a clear explanation and a practical solution, making it highly relatable and valuable to developers and sysadmins.

Summary

The creator encountered an issue where a mounted volume on their DigitalOcean server was not working correctly, despite having sufficient disk space. After investigation, they discovered the problem was related to inode exhaustion, a common issue in Linux when dealing with many small files like those in node_modules. The solution involved reformatting the volume with a higher inode ratio.

Structure

1Problem: Mounted volume not working
2Initial troubleshooting and confusion
3Discovery of inode exhaustion as the cause
4Explanation of how inodes work in Linux
5Solution: Reformatting the volume with more inodes
6Resolution: Volume now working correctly

Product placement

DigitalOcean server and volumes are shown and discussed as the platform where the problem occurred.

Original caption

Mounted volume not working on my server?? #ubuntu #server #devops #linux

More from @daniel.lasek

Their other posts in the index, biggest breakout first.

On-screen text

Mounted volume not working??? SO I JUST MOUNTED A 15 GIGABYTE VOLUME ON MY SERVER AND IT STILL DIDN'T WORK. INVESTIGATE AND I'M LIKE, DUDE, IT CLEARLY SAYS OBVIOUSLY 14 GIGS, I HAVE A 15 GIGABYTE INSTANCE RIGHT HERE. AND WHEN I TRANSFER EVERYTHING, PROJECTS INTO IT, IT FAILED HALFWAY AND ONLY THREE GIGS OR SO WERE BEING USED. AND TURNS OUT IN LINUX, AND FOLDER IN NO MATTER HOW SMALL, REQUIRES AN EXACT ONE I KNOW TO EXIST. SO I RAN THIS COMMAND AND BASICALLY IT TOLD ME HOW MANY I NODES I HAVE, WHICH TURNED OUT TO BE AN ISSUE BECAUSE YOU NODE MODULES IS. A NEW I NODE FOR EVERY FILE. SO THE FIX WAS PRETTY SIMPLE. AND BASICALLY IT JUST TELLS LINUX FOR EVERY 4 KILOBYTES OF SPACE, INDEX. SO NOW BASICALLY I HAVE MILLIONS OF INDEX CARDS IN OF THOUSANDS. SO RIGHT NOW, ONLY 7.2 GIGABYTES ARE ACTUALLY BEING USED. ALL MY PROJECTS NOW AND ONLY 16% OF I NOTES ARE BEING USED. THAT WAS THE ACTUAL ISSUE.

Transcript

Mounted volume not working??? So I just mounted a 15 gigabyte volume on my server and it still didn't work. I'm trying to investigate and I'm like, dude, it clearly says, obviously 14 gigs, but I have a 15 gigabyte instance right here. And when I transfer everything, projects into it, it failed halfway and only three and a half gigs or so were being used. So I did some more digging and turns out, and in Linux, every single file and folder, no matter how small, requires an exact one inode to exist. So I ran this command and basically it told me how many inodes I have, which turned out to be an issue because you, node modules is. It basically makes a new inode for every file. So the fix was pretty simple. I had to run this command and basically it just tells Linux for every 4 kilobytes of space, create an index. So now basically I have millions of index cards instead of thousands. So right now, only 7.2 gigabytes are actually being used. All my projects are in here now and only 16% of inodes are being used. That was the actual issue.