macOS Tahoe 26.6.2 stops writing files below 1 GB free, silently (September 7, 2026)

What broke

The Eclectic Light Company ran a macOS Tahoe 26.6.2 boot volume down until 135.8 MB of free space was left, in a 100 GB virtual machine on a Mac mini M4 Pro. macOS put up a warning notification at around 1 GB. After that, the report says, "most file operations, even creating a new folder, will fail. That applies to all apps, regardless of whether they handle those failures gracefully."

The author treats the failure itself as expected behavior for a volume with nothing left on it, and that is fair. What I would report as the defect is the silence. A screenshot taken on that volume is not saved and nothing complains: the file simply is not there. A document does not save. A new folder is not created. The one notification that named the cause came and went at the 1 GB mark, and after that the system stops explaining itself.

What the log records

The first error logged is ENOSPC, insufficient free space, and it halts writes across every application at once. Spotlight's server recycles and closes its stores. Where physical memory is exhausted at the same time, the report describes the system trying "to allocate space in the VM volume as its backing store for virtual memory, but in the absence of free space to do so, that fails". That is the point at which a Mac stops being merely inconvenient.

macOS does try to dig itself out. The deleted process works through up to three urgency phases of purging, aiming in this test at a freespace goal of about 14.8 GB. I would read that number as the system's own idea of headroom on a 100 GB volume: roughly fifteen times the level at which it warns you.

Who is affected

This is not a beta problem. macOS Tahoe 26.6.2 is a shipping release, and the behavior described is ordinary APFS behavior on a boot volume with no room left, on Apple silicon and on Intel alike. No unusual hardware and no unusual configuration is involved. The only requirement is a disk with nothing left.

The numbers come from a 100 GB test volume, and the report gives the warning point as about 1 GB of free space rather than as a share of the disk. Anyone who habitually runs a Mac close to full is inside the exposed group, whatever the size of that Mac's disk.

What Apple has said

Nothing, as of September 7, 2026. There is no Apple acknowledgement of the silent-failure behavior, no support document that describes it, and no release note I could verify that mentions it. No fix has shipped.

The mainstream Mac coverage that day was about something else. 9to5Mac published twelve articles on September 7, 2026, covering a podcast episode, a Face ID patent suit, WhatsApp AI agents, browser interoperability, Apple TV, a foldable Mac report, iPhone 18 Pro items and deals, and none of them addressed a macOS bug, a security problem or a system update.

So the published record of this failure mode is one first-hand test with logs behind it, and it arrives without a vendor remedy. I am stating that plainly rather than implying more support than exists.

What to do today

In order, on any Mac whose files you care about:

1. Look at free space now, in the Finder or in System Settings, before you need to. 2. Treat the 1 GB warning notification as a stop-work message rather than a reminder: below it, a save you believe succeeded may not have. 3. Get back to double-digit gigabytes free, not to just above the warning. The system's own purge target in this test was about 14.8 GB. 4. Empty the Trash, clear large downloads and move photo and video libraries off the boot volume. 5. Once space is back, reopen and re-save anything you were editing while the volume was full, and retake any screenshot from that window of time, because nothing will have told you it was lost.

The uncomfortable part is step one: this failure is only cheap if you notice the disk before macOS stops reporting. If you would rather not police that by hand: Get XLAnt.