my droplet has only two small sites on it, that total less than 100mb in hard drive space, but the full 20gb hard drive has been used. I’ve checked the log files, but they are not taking up much space.
I managed to trace the disk usage to a single file: /dev/disk/by-label/DOROOT, which I am unable to delete
It occurred to me that DOROOT might be ‘Digital Ocean Root’, so perhaps its something to do with the droplet management?
I tried to read the file but it seems to either be encrypted or the Digital Ocean console is unable to read it. I managed to read the tail of the file which seems to be full of error reports
I am unable to delete the file, and ssh is buggy since the hard drive filled up so I’m having to do everything thru the DO console which is a bit of a pain as you can’t paste passwords into it
help!
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
Stop stop stop!
/dev/disk/by-label/DOROOTisn’t some file. It’s a representation of your disk itself.DOROOTis the default label for the filesystem. If it was deleted… um, actually everything would probably be fine long term. Maybe if you rebooted, or recreated it in recovery mode.What makes you say your disk is full? What’s the output of
df -handdf -hi?Edit: To be less vague,
/dev/disk/by-label/DOROOTis a symlink to a device node, probably/dev/vda1or something. Deleting a critical device node might make your system behave oddly, but it’s just a representation of the device, not the device itself. It wouldn’t delete all your data. You could recreate the node with one command. It may happen automatically next you reboot.Other actions, such as writing a ton of data to the device node, would trash your data for real.
Edit: Edit.