All Topics
All Topics
Technology
Technology
Design
Design
Programming
Programming
Science
Science
News
News
Gaming
Gaming
Entertainment
Entertainment
Business
Business
Finance
Finance
Sports
Sports
Health
Health
Food
Food
Travel
Travel
Art
Art
Music
Music
Books
Books
Education
Education
Politics
Politics
Personal
Personal
No algorithm. No AI slop. No ads. Just RSS. Pro-human. Indie writers. Real journalism. Open web. Chronological. Hand toasted.

Bug in Apple's fsck_hfs on macOS Sequoia Falsely Reports Corruption on Large HFS+ Volumes

By

Kivanc G

18h ago· 8 min readenInsight

Summary

A detailed technical investigation into a bug in Apple's fsck_hfs tool on macOS Sequoia. The tool falsely reports corruption on large HFS+ volumes (24TB+) on machines with 8GB RAM due to a cache exhaustion issue in the extended attributes check. The author walks through their debugging process, including analyzing on-disk structures, tracing system calls, and ultimately identifying the root cause as a memory allocation failure in the B-tree cache. The data itself is not corrupted—only the diagnostic tool is flawed. Machines with 16GB+ RAM are unaffected.

Key quotes

· 3 pulled
Your data is fine — the bug is in the tool, not the filesystem.
fsck_hfs in macOS Sequoia (version hfs-683.x) has a cache exhaustion bug that reports false corruption on large HFS+ volumes.
On machines with 8 GB RAM, volumes of 24 TB or larger trigger 'Couldn't read node' errors during the extended attributes check.
Snippet from the RSS feed
I Found a Bug in Apple’s fsck_hfs — Here’s How I Tracked It Down TL;DR: fsck_hfs in macOS Sequoia (version hfs-683.x) has a cache exhaustion bug that reports false corruption on large HFS+ …

You might also wanna read