Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Disk Utility warning: dir-stats object missing

Hello,


I updated to macOS Sonoma recently and, afterwards, running First Aid on "Data" in Disk Utility shows the following warning:

warning: missing dir-stats object (id 45026142) referenced by 2 files / directories


Here is the full thing:



Running First Aid on “Data” (disk3s5)


Verifying the startup volume will cause this computer to stop responding.


Verifying file system.

Volume could not be unmounted.

Using live mode.

Performing fsck_apfs -n -l -x /dev/rdisk3s5

Checking the container superblock.

Checking the checkpoint with transaction ID 4881059.

Checking the space manager.

Checking the space manager free queue trees.

Checking the object map.

Checking the encryption key structures.

Checking volume /dev/rdisk3s5.

Checking the APFS volume superblock.

The volume Data was formatted by newfs_apfs (1933.80.3) and last modified by apfs_kext (2235.0.13).

Checking the object map.

Checking the snapshot metadata tree.

Checking the snapshot metadata.

Checking the document ID tree.

Checking the fsroot tree.

warning: missing dir-stats object (id 45026142) referenced by 2 files / directories

Checking the extent ref tree.

Checking the file key rolling tree.

Verifying volume object map space.

Verifying allocated space.

The volume /dev/rdisk3s5 with UUID 24B27901-192B-479A-9CE8-D23FFAAA43E9 appears to be OK.

File system check exit code is 0.

Restoring the original state found as mounted.


Operation successful.



Should I be concerned? How would I go about fixing this? Can't find anything online.

MacBook Pro 14″, macOS 14.0

Posted on Oct 9, 2023 6:16 PM

Reply
Question marked as Top-ranking reply

Posted on Dec 2, 2023 5:07 AM

Hello together!


Although the file system exit code outputs the value 0, I am not sure if there is actually NO problem here.


Justification:


For example, under Informationen zu lokalen Schnappschüssen in Time Machine - Apple Support (DE) Apple writes that snapshots are calculated as free, available SSD storage.


However, since these warning messages appeared on my iMac M1 and my MacBook Pro M1 almost simultaneously, my SSD storage has been full of "system files" again and again, as hourly APFS snapshots are now very well deducted from the free, available SSD storage.


Questions:


  1. Which of you also has this conspicuousness / problem?
  2. Did the warning messages (which have now increased to error messages for me) really arise from the installation of Sonoma? In any case from my point of view all these problems occurred on all of my affected iMacs and Macs from the installation of the Synology software (ActiveBackup for Business Client). Does somebody of you use this Synology-App too?


I would be very grateful for your feedback in this regard!

Erste Hilfe auf „Container disk3“ ausführen Während das Startvolume überprüft wird, reagiert der Computer nicht. Speichersystem überprüfen Livemodus verwenden. fsck_apfs -n -x -l /dev/disk0s2 ausführen Den Container-Superblock prüfen … Den Kontrollpunkt mit Transaktions-ID „12082866“ prüfen … Den EFI-Jumpstart-Eintrag prüfen … Den Space-Manager prüfen … Die Space-Manager-Free-Queue-Bäume prüfen … Die Objektzuordnung prüfen … Die Strukturen des Verschlüsselungsschlüssels prüfen … Volume „/dev/rdisk3s1“ wird überprüft. Den APFS-Volume-Superblock prüfen … Das Volume „ActiveBackupforBusiness_Reserved“ wurde durch „storagekitd (2235.41.1)“ formatiert und zuletzt von „apfs_kext (2235.41.1)“ geändert. Die Objektzuordnung prüfen … Den Schnappschuss-Metadatenbaum prüfen … Die Schnappschuss-Metadaten prüfen … Den Fsroot-Baum prüfen … Den Extent-Ref-Baum prüfen … Den File-Key-Rolling-Baum prüfen … Den Object-Map-Platz des Volumes prüfen … Das Volume „/dev/rdisk3s1“ mit der UUID CB477600-2F9F-4435-A36F-2C9A0E90706D ist anscheinend in Ordnung. Volume „/dev/rdisk3s2“ wird überprüft. Den APFS-Volume-Superblock prüfen … Das Volume „Update“ wurde durch „com.apple.Mobile (1677.141.1)“ formatiert und zuletzt von „apfs_kext (2235.41.1)“ geändert. Die Objektzuordnung prüfen … Den Schnappschuss-Metadatenbaum prüfen … Die Schnappschuss-Metadaten prüfen … Den Fsroot-Baum prüfen … Den Extent-Ref-Baum prüfen … Den Object-Map-Platz des Volumes prüfen … Das Volume „/dev/rdisk3s2“ mit der UUID 82B421CC-BCA9-406B-8A62-1FDA7B9F653E ist anscheinend in Ordnung. Volume „/dev/rdisk3s3“ wird überprüft. Den APFS-Volume-Superblock prüfen … Das Volume „Macintosh HD - Daten“ wurde durch „diskmanagementd (1677.141.1)“ formatiert und zuletzt von „apfs_kext (2235.41.1)“ geändert. Die Objektzuordnung prüfen … Den Schnappschuss-Metadatenbaum prüfen … Die Schnappschuss-Metadaten prüfen … Schnappschuss 1 von 5 (com.apple.TimeMachine.2023-11-30-175335.local) prüfen … warning: descendants (351) of dir-stats object (id 87592) is greater than expected (225) warning: snapshot fsroot / file key rolling / doc-id tree corruptions are not repaired; they'll go away once the snapshot is deleted warning: physical_size (1027293184) of dir-stats object (id 87592) is greater than expected (1003302912) warning: descendants (18446744073709551577) of dir-stats object (id 1950496) is greater than expected (3) warning: physical_size (8192) of dir-stats object (id 1950496) is greater than expected (0) warning: physical_size (11071488) of dir-stats object (id 14828829) is greater than expected (10416128) warning: physical_size (112664576) of dir-stats object (id 21429034) is greater than expected (87646208) warning: descendants (108) of dir-stats object (id 27350458) is greater than expected (102) warning: descendants (2883) of dir-stats object (id 31200064) is greater than expected (2235) warning: descendants (100) of dir-stats object (id 31200065) is greater than expected (94) warning: descendants (114) of dir-stats object (id 31385941) is greater than expected (108) warning: descendants (74) of dir-stats object (id 164278569) is greater than expected (63) error: doc-id tree: record exists for doc-id 3213, file-id 111942224 but no inode references this doc-id error: doc-id tree: record exists for doc-id 5084, file-id 178615208 but no inode references this doc-id Schnappschuss 2 von 5 (com.apple.TimeMachine.2023-11-30-194006.local) prüfen … warning: descendants (351) of dir-stats object (id 87592) is greater than expected (225) warning: physical_size (1027293184) of dir-stats object (id 87592) is greater than expected (1003302912) warning: descendants (18446744073709551577) of dir-stats object (id 1950496) is greater than expected (3) warning: physical_size (8192) of dir-stats object (id 1950496) is greater than expected (0) warning: physical_size (11071488) of dir-stats object (id 14828829) is greater than expected (10416128) warning: physical_size (112664576) of dir-stats object (id 21429034) is greater than expected (87646208) warning: descendants (108) of dir-stats object (id 27350458) is greater than expected (102) warning: descendants (2883) of dir-stats object (id 31200064) is greater than expected (2235) warning: descendants (100) of dir-stats object (id 31200065) is greater than expected (94) warning: descendants (114) of dir-stats object (id 31385941) is greater than expected (108) warning: descendants (74) of dir-stats object (id 164278569) is greater than expected (63) error: doc-id tree: record exists for doc-id 3213, file-id 111942224 but no inode references this doc-id error: doc-id tree: record exists for doc-id 5084, file-id 178615208 but no inode references this doc-id Schnappschuss 3 von 5 (com.apple.TimeMachine.2023-12-01-100120.local) prüfen … warning: descendants (351) of dir-stats object (id 87592) is greater than expected (225) warning: physical_size (1027293184) of dir-stats object (id 87592) is greater than expected (1003302912) warning: descendants (18446744073709551577) of dir-stats object (id 1950496) is greater than expected (3) warning: physical_size (8192) of dir-stats object (id 1950496) is greater than expected (0) warning: physical_size (11071488) of dir-stats object (id 14828829) is greater than expected (10416128) warning: physical_size (112664576) of dir-stats object (id 21429034) is greater than expected (87646208) warning: descendants (108) of dir-stats object (id 27350458) is greater than expected (102) warning: descendants (2883) of dir-stats object (id 31200064) is greater than expected (2235) warning: descendants (100) of dir-stats object (id 31200065) is greater than expected (94) warning: descendants (114) of dir-stats object (id 31385941) is greater than expected (108) warning: descendants (74) of dir-stats object (id 164278569) is greater than expected (63) error: doc-id tree: record exists for doc-id 3213, file-id 111942224 but no inode references this doc-id error: doc-id tree: record exists for doc-id 5084, file-id 178615208 but no inode references this doc-id Schnappschuss 4 von 5 (com.apple.TimeMachine.2023-12-01-110720.local) prüfen … warning: descendants (351) of dir-stats object (id 87592) is greater than expected (225) warning: physical_size (1027293184) of dir-stats object (id 87592) is greater than expected (1003302912) warning: descendants (18446744073709551577) of dir-stats object (id 1950496) is greater than expected (3) warning: physical_size (8192) of dir-stats object (id 1950496) is greater than expected (0) warning: physical_size (11071488) of dir-stats object (id 14828829) is greater than expected (10416128) warning: physical_size (112664576) of dir-stats object (id 21429034) is greater than expected (87646208) warning: descendants (108) of dir-stats object (id 27350458) is greater than expected (102) warning: descendants (2883) of dir-stats object (id 31200064) is greater than expected (2235) warning: descendants (100) of dir-stats object (id 31200065) is greater than expected (94) warning: descendants (114) of dir-stats object (id 31385941) is greater than expected (108) warning: descendants (74) of dir-stats object (id 164278569) is greater than expected (63) error: doc-id tree: record exists for doc-id 3213, file-id 111942224 but no inode references this doc-id error: doc-id tree: record exists for doc-id 5084, file-id 178615208 but no inode references this doc-id Schnappschuss 5 von 5 (com.apple.TimeMachine.2023-12-01-120737.local) prüfen … warning: descendants (351) of dir-stats object (id 87592) is greater than expected (225) warning: physical_size (1027293184) of dir-stats object (id 87592) is greater than expected (1003302912) warning: descendants (18446744073709551577) of dir-stats object (id 1950496) is greater than expected (3) warning: physical_size (8192) of dir-stats object (id 1950496) is greater than expected (0) warning: physical_size (11071488) of dir-stats object (id 14828829) is greater than expected (10416128) warning: physical_size (112664576) of dir-stats object (id 21429034) is greater than expected (87646208) warning: descendants (108) of dir-stats object (id 27350458) is greater than expected (102) warning: descendants (2883) of dir-stats object (id 31200064) is greater than expected (2235) warning: descendants (100) of dir-stats object (id 31200065) is greater than expected (94) warning: descendants (114) of dir-stats object (id 31385941) is greater than expected (108) warning: descendants (74) of dir-stats object (id 164278569) is greater than expected (63) error: doc-id tree: record exists for doc-id 3213, file-id 111942224 but no inode references this doc-id error: doc-id tree: record exists for doc-id 5084, file-id 178615208 but no inode references this doc-id Den Dokument-ID-Baum prüfen … Den Fsroot-Baum prüfen … warning: descendants (351) of dir-stats object (id 87592) is greater than expected (225) warning: physical_size (1027293184) of dir-stats object (id 87592) is greater than expected (1003302912) warning: descendants (18446744073709551577) of dir-stats object (id 1950496) is greater than expected (3) warning: physical_size (8192) of dir-stats object (id 1950496) is greater than expected (0) warning: physical_size (11071488) of dir-stats object (id 14828829) is greater than expected (10416128) warning: physical_size (112664576) of dir-stats object (id 21429034) is greater than expected (87646208) warning: descendants (108) of dir-stats object (id 27350458) is greater than expected (102) warning: descendants (2883) of dir-stats object (id 31200064) is greater than expected (2235) warning: descendants (100) of dir-stats object (id 31200065) is greater than expected (94) warning: descendants (114) of dir-stats object (id 31385941) is greater than expected (108) warning: descendants (74) of dir-stats object (id 164278569) is greater than expected (63) error: doc-id tree: record exists for doc-id 3213, file-id 111942224 but no inode references this doc-id error: doc-id tree: record exists for doc-id 5084, file-id 178615208 but no inode references this doc-id Den Extent-Ref-Baum prüfen … Den File-Key-Rolling-Baum prüfen … Den Object-Map-Platz des Volumes prüfen … Das Volume „/dev/rdisk3s3“ mit der UUID B9546E27-DAC8-471C-9349-B041A9D3E8C6 ist offenbar beschädigt und muss repariert werden. Volume „/dev/rdisk3s4“ wird überprüft. Den APFS-Volume-Superblock prüfen … Das Volume „Preboot“ wurde durch „com.apple.Mobile (1677.141.1)“ formatiert und zuletzt von „apfs_kext (2235.41.1)“ geändert. Die Objektzuordnung prüfen … Den Schnappschuss-Metadatenbaum prüfen … Die Schnappschuss-Metadaten prüfen … Den Fsroot-Baum prüfen … Den Extent-Ref-Baum prüfen … Den Object-Map-Platz des Volumes prüfen … Das Volume „/dev/rdisk3s4“ mit der UUID 97757A58-27A2-492B-8805-2BC19AB9AD43 ist anscheinend in Ordnung. Volume „/dev/rdisk3s5“ wird überprüft. Den APFS-Volume-Superblock prüfen … Das Volume „Recovery“ wurde durch „com.apple.Mobile (1677.141.1)“ formatiert und zuletzt von „apfs_kext (2235.41.1)“ geändert. Die Objektzuordnung prüfen … Den Schnappschuss-Metadatenbaum prüfen … Die Schnappschuss-Metadaten prüfen … Den Fsroot-Baum prüfen … Den Extent-Ref-Baum prüfen … Den Object-Map-Platz des Volumes prüfen … Das Volume „/dev/rdisk3s5“ mit der UUID E29CB578-235D-4D05-A970-C1369A382403 ist anscheinend in Ordnung. Volume „/dev/rdisk3s6“ wird überprüft. Den APFS-Volume-Superblock prüfen … Das Volume „VM“ wurde durch „com.apple.Mobile (1677.141.1)“ formatiert und zuletzt von „apfs_kext (2235.41.1)“ geändert. Die Objektzuordnung prüfen … Den Schnappschuss-Metadatenbaum prüfen … Die Schnappschuss-Metadaten prüfen … Den Fsroot-Baum prüfen … Den Extent-Ref-Baum prüfen … Den Object-Map-Platz des Volumes prüfen … Das Volume „/dev/rdisk3s6“ mit der UUID 8C6D2451-093E-4D2E-9140-2C9177D9EC68 ist anscheinend in Ordnung. Volume „/dev/rdisk3s7“ wird überprüft. Den APFS-Volume-Superblock prüfen … Das Volume „Macintosh HD“ wurde durch „com.apple.Mobile (1677.141.1)“ formatiert und zuletzt von „apfs_kext (2235.41.1)“ geändert. Die Objektzuordnung prüfen … Den Schnappschuss-Metadatenbaum prüfen … Die Schnappschuss-Metadaten prüfen … Schnappschuss 1 von 1 (com.apple.os.update-E071D10CC651CAA7FA82B6ABD01FB1E761A267F6EA0104F2743F887F5B4BCC8C) prüfen … Den Fsroot-Baum prüfen … Den File-Extent-Baum prüfen … Den Extent-Ref-Baum prüfen … Den Object-Map-Platz des Volumes prüfen … Das Volume „/dev/rdisk3s7“ mit der UUID 75570AC5-E3D4-44B2-BB18-52A0DDBEAC8E ist anscheinend in Ordnung. Zugeordneten Platz überprüfen … Verschobene Reparaturen durchführen … warning: descendants of dir-stats object (id 87592) does not match expected value (225) Skipped 7/7 repairs of this type in total. warning: physical size of dir-stats object (id 87592) does not match expected value (1003302912) Skipped 4/4 repairs of this type in total. warning: doc-id tree record exists for doc-id 3213, but no inode references this doc-id Skipped 2/2 repairs of this type in total. Der Container „/dev/disk0s2“ ist anscheinend OK. Exit-Code für Speichersystemprüfung lautet 0. Vorgang erfolgreich.


18 replies
Sort By: 
Question marked as Top-ranking reply

Dec 2, 2023 5:07 AM in response to DoubleW

Hello together!


Although the file system exit code outputs the value 0, I am not sure if there is actually NO problem here.


Justification:


For example, under Informationen zu lokalen Schnappschüssen in Time Machine - Apple Support (DE) Apple writes that snapshots are calculated as free, available SSD storage.


However, since these warning messages appeared on my iMac M1 and my MacBook Pro M1 almost simultaneously, my SSD storage has been full of "system files" again and again, as hourly APFS snapshots are now very well deducted from the free, available SSD storage.


Questions:


  1. Which of you also has this conspicuousness / problem?
  2. Did the warning messages (which have now increased to error messages for me) really arise from the installation of Sonoma? In any case from my point of view all these problems occurred on all of my affected iMacs and Macs from the installation of the Synology software (ActiveBackup for Business Client). Does somebody of you use this Synology-App too?


I would be very grateful for your feedback in this regard!

Erste Hilfe auf „Container disk3“ ausführen Während das Startvolume überprüft wird, reagiert der Computer nicht. Speichersystem überprüfen Livemodus verwenden. fsck_apfs -n -x -l /dev/disk0s2 ausführen Den Container-Superblock prüfen … Den Kontrollpunkt mit Transaktions-ID „12082866“ prüfen … Den EFI-Jumpstart-Eintrag prüfen … Den Space-Manager prüfen … Die Space-Manager-Free-Queue-Bäume prüfen … Die Objektzuordnung prüfen … Die Strukturen des Verschlüsselungsschlüssels prüfen … Volume „/dev/rdisk3s1“ wird überprüft. Den APFS-Volume-Superblock prüfen … Das Volume „ActiveBackupforBusiness_Reserved“ wurde durch „storagekitd (2235.41.1)“ formatiert und zuletzt von „apfs_kext (2235.41.1)“ geändert. Die Objektzuordnung prüfen … Den Schnappschuss-Metadatenbaum prüfen … Die Schnappschuss-Metadaten prüfen … Den Fsroot-Baum prüfen … Den Extent-Ref-Baum prüfen … Den File-Key-Rolling-Baum prüfen … Den Object-Map-Platz des Volumes prüfen … Das Volume „/dev/rdisk3s1“ mit der UUID CB477600-2F9F-4435-A36F-2C9A0E90706D ist anscheinend in Ordnung. Volume „/dev/rdisk3s2“ wird überprüft. Den APFS-Volume-Superblock prüfen … Das Volume „Update“ wurde durch „com.apple.Mobile (1677.141.1)“ formatiert und zuletzt von „apfs_kext (2235.41.1)“ geändert. Die Objektzuordnung prüfen … Den Schnappschuss-Metadatenbaum prüfen … Die Schnappschuss-Metadaten prüfen … Den Fsroot-Baum prüfen … Den Extent-Ref-Baum prüfen … Den Object-Map-Platz des Volumes prüfen … Das Volume „/dev/rdisk3s2“ mit der UUID 82B421CC-BCA9-406B-8A62-1FDA7B9F653E ist anscheinend in Ordnung. Volume „/dev/rdisk3s3“ wird überprüft. Den APFS-Volume-Superblock prüfen … Das Volume „Macintosh HD - Daten“ wurde durch „diskmanagementd (1677.141.1)“ formatiert und zuletzt von „apfs_kext (2235.41.1)“ geändert. Die Objektzuordnung prüfen … Den Schnappschuss-Metadatenbaum prüfen … Die Schnappschuss-Metadaten prüfen … Schnappschuss 1 von 5 (com.apple.TimeMachine.2023-11-30-175335.local) prüfen … warning: descendants (351) of dir-stats object (id 87592) is greater than expected (225) warning: snapshot fsroot / file key rolling / doc-id tree corruptions are not repaired; they'll go away once the snapshot is deleted warning: physical_size (1027293184) of dir-stats object (id 87592) is greater than expected (1003302912) warning: descendants (18446744073709551577) of dir-stats object (id 1950496) is greater than expected (3) warning: physical_size (8192) of dir-stats object (id 1950496) is greater than expected (0) warning: physical_size (11071488) of dir-stats object (id 14828829) is greater than expected (10416128) warning: physical_size (112664576) of dir-stats object (id 21429034) is greater than expected (87646208) warning: descendants (108) of dir-stats object (id 27350458) is greater than expected (102) warning: descendants (2883) of dir-stats object (id 31200064) is greater than expected (2235) warning: descendants (100) of dir-stats object (id 31200065) is greater than expected (94) warning: descendants (114) of dir-stats object (id 31385941) is greater than expected (108) warning: descendants (74) of dir-stats object (id 164278569) is greater than expected (63) error: doc-id tree: record exists for doc-id 3213, file-id 111942224 but no inode references this doc-id error: doc-id tree: record exists for doc-id 5084, file-id 178615208 but no inode references this doc-id Schnappschuss 2 von 5 (com.apple.TimeMachine.2023-11-30-194006.local) prüfen … warning: descendants (351) of dir-stats object (id 87592) is greater than expected (225) warning: physical_size (1027293184) of dir-stats object (id 87592) is greater than expected (1003302912) warning: descendants (18446744073709551577) of dir-stats object (id 1950496) is greater than expected (3) warning: physical_size (8192) of dir-stats object (id 1950496) is greater than expected (0) warning: physical_size (11071488) of dir-stats object (id 14828829) is greater than expected (10416128) warning: physical_size (112664576) of dir-stats object (id 21429034) is greater than expected (87646208) warning: descendants (108) of dir-stats object (id 27350458) is greater than expected (102) warning: descendants (2883) of dir-stats object (id 31200064) is greater than expected (2235) warning: descendants (100) of dir-stats object (id 31200065) is greater than expected (94) warning: descendants (114) of dir-stats object (id 31385941) is greater than expected (108) warning: descendants (74) of dir-stats object (id 164278569) is greater than expected (63) error: doc-id tree: record exists for doc-id 3213, file-id 111942224 but no inode references this doc-id error: doc-id tree: record exists for doc-id 5084, file-id 178615208 but no inode references this doc-id Schnappschuss 3 von 5 (com.apple.TimeMachine.2023-12-01-100120.local) prüfen … warning: descendants (351) of dir-stats object (id 87592) is greater than expected (225) warning: physical_size (1027293184) of dir-stats object (id 87592) is greater than expected (1003302912) warning: descendants (18446744073709551577) of dir-stats object (id 1950496) is greater than expected (3) warning: physical_size (8192) of dir-stats object (id 1950496) is greater than expected (0) warning: physical_size (11071488) of dir-stats object (id 14828829) is greater than expected (10416128) warning: physical_size (112664576) of dir-stats object (id 21429034) is greater than expected (87646208) warning: descendants (108) of dir-stats object (id 27350458) is greater than expected (102) warning: descendants (2883) of dir-stats object (id 31200064) is greater than expected (2235) warning: descendants (100) of dir-stats object (id 31200065) is greater than expected (94) warning: descendants (114) of dir-stats object (id 31385941) is greater than expected (108) warning: descendants (74) of dir-stats object (id 164278569) is greater than expected (63) error: doc-id tree: record exists for doc-id 3213, file-id 111942224 but no inode references this doc-id error: doc-id tree: record exists for doc-id 5084, file-id 178615208 but no inode references this doc-id Schnappschuss 4 von 5 (com.apple.TimeMachine.2023-12-01-110720.local) prüfen … warning: descendants (351) of dir-stats object (id 87592) is greater than expected (225) warning: physical_size (1027293184) of dir-stats object (id 87592) is greater than expected (1003302912) warning: descendants (18446744073709551577) of dir-stats object (id 1950496) is greater than expected (3) warning: physical_size (8192) of dir-stats object (id 1950496) is greater than expected (0) warning: physical_size (11071488) of dir-stats object (id 14828829) is greater than expected (10416128) warning: physical_size (112664576) of dir-stats object (id 21429034) is greater than expected (87646208) warning: descendants (108) of dir-stats object (id 27350458) is greater than expected (102) warning: descendants (2883) of dir-stats object (id 31200064) is greater than expected (2235) warning: descendants (100) of dir-stats object (id 31200065) is greater than expected (94) warning: descendants (114) of dir-stats object (id 31385941) is greater than expected (108) warning: descendants (74) of dir-stats object (id 164278569) is greater than expected (63) error: doc-id tree: record exists for doc-id 3213, file-id 111942224 but no inode references this doc-id error: doc-id tree: record exists for doc-id 5084, file-id 178615208 but no inode references this doc-id Schnappschuss 5 von 5 (com.apple.TimeMachine.2023-12-01-120737.local) prüfen … warning: descendants (351) of dir-stats object (id 87592) is greater than expected (225) warning: physical_size (1027293184) of dir-stats object (id 87592) is greater than expected (1003302912) warning: descendants (18446744073709551577) of dir-stats object (id 1950496) is greater than expected (3) warning: physical_size (8192) of dir-stats object (id 1950496) is greater than expected (0) warning: physical_size (11071488) of dir-stats object (id 14828829) is greater than expected (10416128) warning: physical_size (112664576) of dir-stats object (id 21429034) is greater than expected (87646208) warning: descendants (108) of dir-stats object (id 27350458) is greater than expected (102) warning: descendants (2883) of dir-stats object (id 31200064) is greater than expected (2235) warning: descendants (100) of dir-stats object (id 31200065) is greater than expected (94) warning: descendants (114) of dir-stats object (id 31385941) is greater than expected (108) warning: descendants (74) of dir-stats object (id 164278569) is greater than expected (63) error: doc-id tree: record exists for doc-id 3213, file-id 111942224 but no inode references this doc-id error: doc-id tree: record exists for doc-id 5084, file-id 178615208 but no inode references this doc-id Den Dokument-ID-Baum prüfen … Den Fsroot-Baum prüfen … warning: descendants (351) of dir-stats object (id 87592) is greater than expected (225) warning: physical_size (1027293184) of dir-stats object (id 87592) is greater than expected (1003302912) warning: descendants (18446744073709551577) of dir-stats object (id 1950496) is greater than expected (3) warning: physical_size (8192) of dir-stats object (id 1950496) is greater than expected (0) warning: physical_size (11071488) of dir-stats object (id 14828829) is greater than expected (10416128) warning: physical_size (112664576) of dir-stats object (id 21429034) is greater than expected (87646208) warning: descendants (108) of dir-stats object (id 27350458) is greater than expected (102) warning: descendants (2883) of dir-stats object (id 31200064) is greater than expected (2235) warning: descendants (100) of dir-stats object (id 31200065) is greater than expected (94) warning: descendants (114) of dir-stats object (id 31385941) is greater than expected (108) warning: descendants (74) of dir-stats object (id 164278569) is greater than expected (63) error: doc-id tree: record exists for doc-id 3213, file-id 111942224 but no inode references this doc-id error: doc-id tree: record exists for doc-id 5084, file-id 178615208 but no inode references this doc-id Den Extent-Ref-Baum prüfen … Den File-Key-Rolling-Baum prüfen … Den Object-Map-Platz des Volumes prüfen … Das Volume „/dev/rdisk3s3“ mit der UUID B9546E27-DAC8-471C-9349-B041A9D3E8C6 ist offenbar beschädigt und muss repariert werden. Volume „/dev/rdisk3s4“ wird überprüft. Den APFS-Volume-Superblock prüfen … Das Volume „Preboot“ wurde durch „com.apple.Mobile (1677.141.1)“ formatiert und zuletzt von „apfs_kext (2235.41.1)“ geändert. Die Objektzuordnung prüfen … Den Schnappschuss-Metadatenbaum prüfen … Die Schnappschuss-Metadaten prüfen … Den Fsroot-Baum prüfen … Den Extent-Ref-Baum prüfen … Den Object-Map-Platz des Volumes prüfen … Das Volume „/dev/rdisk3s4“ mit der UUID 97757A58-27A2-492B-8805-2BC19AB9AD43 ist anscheinend in Ordnung. Volume „/dev/rdisk3s5“ wird überprüft. Den APFS-Volume-Superblock prüfen … Das Volume „Recovery“ wurde durch „com.apple.Mobile (1677.141.1)“ formatiert und zuletzt von „apfs_kext (2235.41.1)“ geändert. Die Objektzuordnung prüfen … Den Schnappschuss-Metadatenbaum prüfen … Die Schnappschuss-Metadaten prüfen … Den Fsroot-Baum prüfen … Den Extent-Ref-Baum prüfen … Den Object-Map-Platz des Volumes prüfen … Das Volume „/dev/rdisk3s5“ mit der UUID E29CB578-235D-4D05-A970-C1369A382403 ist anscheinend in Ordnung. Volume „/dev/rdisk3s6“ wird überprüft. Den APFS-Volume-Superblock prüfen … Das Volume „VM“ wurde durch „com.apple.Mobile (1677.141.1)“ formatiert und zuletzt von „apfs_kext (2235.41.1)“ geändert. Die Objektzuordnung prüfen … Den Schnappschuss-Metadatenbaum prüfen … Die Schnappschuss-Metadaten prüfen … Den Fsroot-Baum prüfen … Den Extent-Ref-Baum prüfen … Den Object-Map-Platz des Volumes prüfen … Das Volume „/dev/rdisk3s6“ mit der UUID 8C6D2451-093E-4D2E-9140-2C9177D9EC68 ist anscheinend in Ordnung. Volume „/dev/rdisk3s7“ wird überprüft. Den APFS-Volume-Superblock prüfen … Das Volume „Macintosh HD“ wurde durch „com.apple.Mobile (1677.141.1)“ formatiert und zuletzt von „apfs_kext (2235.41.1)“ geändert. Die Objektzuordnung prüfen … Den Schnappschuss-Metadatenbaum prüfen … Die Schnappschuss-Metadaten prüfen … Schnappschuss 1 von 1 (com.apple.os.update-E071D10CC651CAA7FA82B6ABD01FB1E761A267F6EA0104F2743F887F5B4BCC8C) prüfen … Den Fsroot-Baum prüfen … Den File-Extent-Baum prüfen … Den Extent-Ref-Baum prüfen … Den Object-Map-Platz des Volumes prüfen … Das Volume „/dev/rdisk3s7“ mit der UUID 75570AC5-E3D4-44B2-BB18-52A0DDBEAC8E ist anscheinend in Ordnung. Zugeordneten Platz überprüfen … Verschobene Reparaturen durchführen … warning: descendants of dir-stats object (id 87592) does not match expected value (225) Skipped 7/7 repairs of this type in total. warning: physical size of dir-stats object (id 87592) does not match expected value (1003302912) Skipped 4/4 repairs of this type in total. warning: doc-id tree record exists for doc-id 3213, but no inode references this doc-id Skipped 2/2 repairs of this type in total. Der Container „/dev/disk0s2“ ist anscheinend OK. Exit-Code für Speichersystemprüfung lautet 0. Vorgang erfolgreich.


Reply

Mar 24, 2024 7:15 AM in response to Keksi

Keksi wrote:

I encourage you to contemplate by yourself the purpose of warnings in general. Be it your body, your car, your computer disk or whatever.

I'd rather take a warning seriously, before something worse happens.

I already know what a warning is in log files. It has really little to do with what a “warning” means in other contexts.

Reply

Oct 29, 2023 2:47 PM in response to HWTech

well-after only using mac since IIplus- and never had such an issue despite monthly or so checks with first aid, and recently updating my 2020 MI mini to Sonoma, I got the mentioned " warnings "-

So tried tech tool 18, and updated ONYX and dumped a few very old ( 2004 or so files ) i gave up fixing anything.


So made a backup copy on two different ssd discs and also on older mini ( 2018) and started over. Had a miserable time- but finally got redone with ventura. In the process google drive showed up and took a while to get rid of it when signed on. Had to redo a few gmail sign ins. So now most works OK- but still having problems with a erased OTG to make a new disk backup re time machine. And now must somehow back out 1 password update I did for sonoma to get it to work with ventura. carbon copy worked restoring a partitioned disk portion

of Mac HD startup disk OK. Had hoped to update to sonoma AFTER making time machine backup- but may just abandon such for now. Methinks a bug or two re sonoma file system may be the problem. At least nothing but a day or two of time lost. Disk utility now says all OK.


Reply

Dec 13, 2023 5:11 AM in response to HWTech

This is not about the excessive definition of subtleties, but about increasingly serious problems and malfunctions on an increasing number of affected systems.


In other words, the aforementioned problems and malfunctions will not be solved as soon as perhaps even I am smart enough at some point to understand the subtleties of the above definitions.


My post, which can be seen above, is not formulated exactly like this without reason and you have not answered my really important questions. It would be nice if you no longer respond to these lines, but give other community members the opportunity to help me with information about similar experiences if possible.


Regardless of terms such as "Purgeable" and "Available", the SSD of my or our iMacs and MacBooks never ran to the incapacity of function with snapshot files before the malfunctions outlined above occurred. MacOS prompts us to delete snapshots every few days on all affected devices, otherwise the functionality of the system is no longer guaranteed. Normally, the oldest versions are inconspicuously replaced in the background by the latest ones and snapshots are not displayed as occupied SSD storage space.


The problems began with the upgrade to MacOS Sonoma and/or the update/upgrade to the last 2 or 3 versions of the Mac client of Synology Active Backup for Business. The file system errors caused by this are clearly the cause of the incorrect snapshot handling.

Reply

Dec 2, 2023 5:38 PM in response to Stephan_Al

Stephan_Al wrote:

Hello together!

Although the file system exit code outputs the value 0, I am not sure if there is actually NO problem here.

Errors are bad and need to be repaired. If the errors cannot be repaired even from Recovery Mode, then the disk needs to be erased in order to create a new clean file system and macOS reinstalled followed by restoring from a backup.


Warnings on the other hand I don't believe are a problem and can be ignored.....for most situations anyway.


As I mentioned in an earlier post, First Aid summary is known to lie about the results as you have just found out with those actual errors not showing as repaired.



Justification:

For example, under Informationen zu lokalen Schnappschüssen in Time Machine - Apple Support (DE) Apple writes that snapshots are calculated as free, available SSD storage.

However, since these warning messages appeared on my iMac M1 and my MacBook Pro M1 almost simultaneously, my SSD storage has been full of "system files" again and again, as hourly APFS snapshots are now very well deducted from the free, available SSD storage.

I highlighted two items in your post here "free, available" because in macOS there is a huge difference between Free storage space and Available storage space. I find Apple's choice of using "Available" to be unfortunate since it is very misleading even if it is technically an accurate designation, but the average user won't realize they are viewing the Available space incorrectly.


Free space is the storage area that can be used immediately while the Available space is a mix of Free space + Purgeable space. Purgeable space is storage that will be released to the user at some unknown point in the future. Since Available storage space consists of Purgeable space, that means many times what is listed as Available space is not really usable by anyone since it is already in use by the system. Now there are times when you may see the Available space nearly matches the Free space, but most times the Available space will consist of a significant amount of Purgeable space that is still being actively used by the system.


Free space = Available - Purgeable


Available = Free + Purgeable.


Also you quoted the Apple TM article with an incorrect English translation regarding the storage space. I'm going to post the same section from the English version of the article:


About Time Machine local snapshots - Apple Support

How local snapshots use storage space

You don't need to think about how much storage space local snapshots are using, because they don't use space needed for tasks like downloading files, copying files, or installing new software. In fact, your Mac counts the space used by snapshots as available storage.

Even so, Time Machine stores snapshots only on disks that have plenty of free space, and it automatically deletes snapshots as they age or as space is needed for other things.

Notice I highlighted locations in the quote of the English TM article for Free and Available storage space. I think it makes a little more sense now that I properly defined the two terms as Apple is using them in macOS and in this quoted portion of the Apple TM article.


APFS snapshots do take up storage space since "TM only stores snapshots on disk that have plenty of Free space".....why does Apple mention "plenty of Free space" if snapshot don't take up storage?


I think even Apple doesn't really know how to properly communicate about how storage is viewed in macOS, because technically the following quote from the TM article:

In fact, your Mac counts the space used by snapshots as available storage.


is not entirely correct. Apple should be also mentioning "Purgeable" in that quote alongside "Available".


I really wish Apple would have macOS clearly show Free and Purgeable space only instead of including the reference to Available space, since Free & Purgeable are much easier to understand for most people since users make the mistake of thinking Available means Free which it does not.

Reply

Jan 30, 2024 6:03 AM in response to barisrobinson

barisrobinson wrote:

Hello all,

l’ve updated my Apple Macbook pro M1 a while ago to macOS Sonoma, it was running fine until today, something unusual happened. The situation is, when l turn on my laptop it comes to the point where l type my password just fine but after that all l see is a blank desktop with the wallpaper image, no thumbnails, no apps reachable. You can move the cursor, but l couldn’t find anything to do with that. When l start it up in recovery mode and do first aid in disk utility to APFS Data Volume l see the Disk Utility warning dir-stat object missing. I have already tried reinstalling Sonoma yet nothing has changed. My questions are :

While you may be seeing a similar error with First Aid your system seems to be having boot issues unlike the OP's. You really should start your own thread to deal with the issue.


1 - I’ve some important data that l would love to recover, l’ve already tried starting it up while pressing T key to get in to Target Disk Mode but it is not happening. Would there be another way to do that ?

That startup key combination is for Intel Macs. For Apple Silicon Macs, all the special startup modes are accessed through the new Options boot screen you accessed for Recovery Mode. Here is an Apple article with instructions for accessing Target Disk Mode:

Transfer files between two Mac computers using target disk mode - Apple Support

If the computer is on, choose Apple menu  > System Settings, then click General  in the sidebar (you may need to scroll down). Click Startup Disk on the right, then click Restart in Target Disk Mode.

Unfortunately those instructions do not distinguish between Intel & Apple Silicon Macs which is why I quoted the relevant section, although you should read the linked article since it provides information about needing to use a Thunderbolt cable connection (USB is no longer an option for the connection).


2 - Is this a hardware problem ? Do l need to take it to a certified Apple Service ?

No idea, maybe.


Any help is extremely appreciated. I am aware of the fact that l should have regularly backed up my computer, l’ve been using various Mac computers for over 15 years never find myself in a situation as such, too much trust l guess. Looking forward to hear from you.

With the 2016+ Macs there are a lot of new ways to permanently lose access to your data if it is not backed up due to all of the hardware, software, and security changes Apple has implemented in their products. Plus, it is impossible to recover accidentally deleted data after the Trash has been emptied due to how SSDs work.



Reply

Oct 10, 2023 8:48 AM in response to DoubleW

DoubleW wrote:


Hello,


I updated to macOS Sonoma recently and, afterwards, running First Aid on "Data" in Disk Utility shows the following warning:

warning: missing dir-stats object (id 45026142) referenced by 2 files / directories




The volume /dev/rdisk3s5 with UUID 24B27901-192B-479A-9CE8-D23FFAAA43E9 appears to be OK.
File system check exit code is 0.
Restoring the original state found as mounted.

Operation successful.


Should I be concerned? How would I go about fixing this? Can't find anything online.


Why are you running First Aid(?) Are you having some issue?


If it ain't broke don't fix it.


please note—

The complete report returns no issue:


File system check exit code is 0



I would agree to simply ignore it.

Reply

Oct 22, 2023 10:45 PM in response to DoubleW

Running first aid mac mini m1 2020 version sonoma

same problem

warning: descendants (6459) of dir-stats object (id 260063) is greater than expected (3052)

warning: descendants (69) of dir-stats object (id 816756) is greater than expected (58)

etc

then Checking the extent ref tree.

Checking the file key rolling tree.

Verifying volume object map space.

The volume /dev/rdisk3s5 with UUID B117D4EE-AAE0-4178-AE63-D3FDE8DDF1E1 was found to be corrupt and needs to be repaired.

Verifying allocated space.

Performing deferred repairs.

The volume /dev/rdisk3s5 with UUID B117D4EE-AAE0-4178-AE63-D3FDE8DDF1E1 appears to be OK.

File system check exit code is 0.


tried onyx to clear no help

tech tool 18 updated shows all ok


So what now ?

Reply

Oct 23, 2023 7:43 AM in response to Barney-15E

Barney-15E wrote:

It's just a warning. It doesn't mean anything is wrong. That would be an error.

Most likely correct, but hard to say with only a portion of the log...this is not the OP so we don't have all the information.


Your scan found some errors and fixed them resulting in "appears to be OK."

No, the First Aid summary will lie about the "Ok" part. I have had several Macs where First Aid said everything was "Ok", but did not repair any of the actual errors it had found. The external volume for one was giving us major issues, including causing Kernel Panics almost every time macOS tried to mount it....the physical drive was fine and the issues disappeared completely after erasing the volume. Each time there were errors listed which were not actually repaired, out drive had issues....usually system performance issues if it occurred on the boot volume.


I do ignore the unfixed "warnings" First Aid reports unless I've exhausted everything else. Regardless, the only way to fix APFS file system issues which are not repaired by First Aid is to erase the whole APFS volume (personally I would erase the whole Container/Volume Group if those file system issues were causing a real problem).


Unfortunately we don't have enough details from @ARBE2 to know for sure either way.

Reply

Dec 15, 2023 6:44 PM in response to Stephan_Al

Stephan_Al wrote:

My post, which can be seen above, is not formulated exactly like this without reason and you have not answered my really important questions.

And what exactly are those questions that have not been answered?


It would be nice if you no longer respond to these lines, but give other community members the opportunity to help me with information about similar experiences if possible.

I thought I was directly addressing your concerns since I quoted each section & responded directly to everything you posted.


Most of your problems are due to not having sufficient Free storage space on the drive.


This will be my last response here. Since none of the other contributors are adding anything else, it seems they believe your questions have been sufficiently answered as well. Just because you don't receive the answer/response you were expecting does not mean your questions have not been sufficiently answered here.


Regardless of terms such as "Purgeable" and "Available", the SSD of my or our iMacs and MacBooks never ran to the incapacity of function with snapshot files before the malfunctions outlined above occurred.

Maybe that is because you never ran out of Free space before.


MacOS prompts us to delete snapshots every few days on all affected devices, otherwise the functionality of the system is no longer guaranteed. Normally, the oldest versions are inconspicuously replaced in the background by the latest ones and snapshots are not displayed as occupied SSD storage space.

The problems began with the upgrade to MacOS Sonoma and/or the update/upgrade to the last 2 or 3 versions of the Mac client of Synology Active Backup for Business. The file system errors caused by this are clearly the cause of the incorrect snapshot handling.

Then you may need to address these issues with Synology if you are using their software to manage backups. It is possible the Synology software is not fully compatible with Sonoma yet. The Synology app is in charge of its own snapshots. The only part Apple plays here is in providing Synology the ability to create & delete snapshots easily. Even if the Synology software is relying on some macOS timing feature with the snapshot retention, then that issue is still Synology's problem to deal with....either by working with Apple to fix the bug, or by providing a Synology mechanism to ensure snapshots are deleted on schedule.


I hope you are able to resolve the issues with your system and any unanswered questions. Good luck.


Reply

Jan 30, 2024 4:01 AM in response to DoubleW

Hello all,


l’ve updated my Apple Macbook pro M1 a while ago to macOS Sonoma, it was running fine until today, something unusual happened. The situation is, when l turn on my laptop it comes to the point where l type my password just fine but after that all l see is a blank desktop with the wallpaper image, no thumbnails, no apps reachable. You can move the cursor, but l couldn’t find anything to do with that. When l start it up in recovery mode and do first aid in disk utility to APFS Data Volume l see the Disk Utility warning dir-stat object missing. I have already tried reinstalling Sonoma yet nothing has changed. My questions are :


1 - I’ve some important data that l would love to recover, l’ve already tried starting it up while pressing T key to get in to Target Disk Mode but it is not happening. Would there be another way to do that ?


2 - Is this a hardware problem ? Do l need to take it to a certified Apple Service ?


Any help is extremely appreciated. I am aware of the fact that l should have regularly backed up my computer, l’ve been using various Mac computers for over 15 years never find myself in a situation as such, too much trust l guess. Looking forward to hear from you.

Best,

B.Robinson

Reply

Disk Utility warning: dir-stats object missing

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.