>get warning that there's 0 bytes of available space on my hdd >don't think much of it as i usually am pretty low on free space >delete some GB of unused stuff >3 minutes later, get warning that there's 0 byte of available space >start sweating buckets >plug in backup drive and start syncing immediately >while syncing is in progress delete another 2GB large file >immediately check available space >0 byte
No idea what's going on. How fucked am I? Are the files I'm backing up now even safe? SMART values show nothing out of the ordinary. Everything seems to work except for things that need a tiny bit of free space.
I'm not currently backing up corrupted data, am I?
Install process hacker and see what's writing unless there's some obvious source. Pretty sure windows doesn't have issues with completely fucking up on reboot if you fill the drive anymore. But that's not certain.
OP here, on phone now. Backup is still running but everything else is getting more erratic with every minute. Forgot to mention that I'm on Debian. Still no idea what's going on.
Luis Anderson
boot into a linux live usb and back up from there to ensure you aren't a victim of some fucked up windows process
Carter Carter
>Linux FREETARDS BTFO HAHAHAAHAHAAHA
Jaxson Thomas
I am impressed that you're actually so fucking dumb that your first action was starting to back up an infinitely filling disk instead of of using iotop and a disk space analyzer to figure out what creates the data and where.
Noah Hernandez
Have you tried looking at dmesg? Also it might be somthing with journaling/logging, I experienced a few years ago a really bad one with systemd's journal whatever. Check how big /var/log is.
Juan Lewis
what's that picture from?
Henry Harris
Disk Space analyzer shows free space, but no program can use it.
/var/log is 15gig. That sounds off, but I don't know what a regular value is.
Carson Morales
Sick blogpost, bro!
Lucas Cooper
are you sure you're not downloading 1 petabyte of porn with your super speed internet?
