Friday, December 22, 2023
HomeAppleexhausting drive - “No area left on system.” in macOS Sonoma 14.2.1...

exhausting drive – “No area left on system.” in macOS Sonoma 14.2.1 (23C71) however there clearly is 131GB on system. What occurred?


Brief Story: Why was my MacBook Air displaying “No area left on system.” and blocking quite simple file writes after I clearly had 131 GB accessible? And why did it clear up after reboot which then confirmed 157 GB accessible?

FWIW, I used to be importing (from the command line) a reasonably large (26GB) MySQL database on the time this occurred. Might which have contributed to this taking place? I’ve imported snapshots of this DB pretty commonly up to now with out problem. Why did snag me now?


Longer Story: I simply had a very unusual factor occur. I’m utilizing macOS Sonoma 14.2.1 on a 2022 MacBook Air with a 512GB SSD and 16GB of RAM.

Whereas performing some fundamental, light-weight work with Chic Textual content 3 and Git (2.43.0; put in via Homebrew) I git a Notification Middle alert saying:

“No area left on system.”

Ha! Foolish macOS! I test my free area on my important drive and see it had 131 GB accessible. What do you imply “no area left on system?”

Then I am going an do a git commit -a -m "Some message." and it provides me an identical message about not having the ability to write to the system as a result of the system is full?

I test the primary system drive once more and make sure: 131 GB accessible.

Beginning to get involved I hook up my exterior Time Machine disk to take a backup; generally I suppose the native Time Machine backups would possibly be taking over area and that may be cleared up by hooking the exterior Time Machine disk.

What occurs? Time Machine fails to again something up.

So I do what any cheap individual would do and rebooted the machine.

When it got here up issues labored as anticipated however now my important system drives exhibits: 157 GB accessible.

Huh? What occurred? Why did I get “No area left on system.” messages with 131 GB accessible and why did my accessible area leap to 157 GB accessible after reboot?

I perceive that “free area” on the primary macOS system drive is an phantasm because of every kind of LVM partitions and such, however what would have precipitated “No area left on system.” when there was nothing actually filling the system?



Supply hyperlink

RELATED ARTICLES

LEAVE A REPLY

Please enter your comment!
Please enter your name here

- Advertisment -
Google search engine

Most Popular

Recent Comments