3 ms·
I regularly run my Windows 10 NTFS drive down to 0 bytes free. I'm always amazed at how the file system survives just fine, but the machine doesn't even crash!
by tredre3 3y ago
I regularly run my Windows 10 NTFS drive down to 0 bytes free.
I'm always amazed at how the file system survives just fine, but the machine doesn't even crash!
I'm not sure where you got your experience from.
- bloomingeek 3y agoI tried, accidentally, to over fill the HDD on a Windows Vista machine. Vista popped up a box telling me I couldn't do it. Unfortunately, in my panic, I didn't take a picture of the warning for posterity.
- caseyy 3y agoMy work demands that I generate large amounts of data and I don’t know how much I’ll have to generate up-front. So I run out of disk space a lot. My experience is that Windows and many of its programs will become very unstable with 0 b on the system drive. And about 3 times out of maybe 50, the system also became unbootable. I’ve learned to do whatever I can to free up space before restarting for stability. The last time I’d regularly run out of space on Win was around Windows 98 times. I never had a problem then. Now in Windows 11 times, it’s a real headache. Not sure how you’re so lucky.
- comex 3y agoI’ve done the same on my Mac perhaps twice in the last few years. Like you, I encountered no crash or any other obvious consequences… I just deleted data and moved on. Though I didn’t try leaving it with zero bytes free for an extended amount of time, or rebooting. Who knows what would happen then. Still, whatever this APFS bug is, the conditions to trigger it are more specific than just filling up the disk.