Want to highlight a helpful answer? Upvote!

Did someone help you, or did an answer or User Tip resolve your issue? Upvote by selecting the upvote arrow. Your feedback helps others! Learn more about when to upvote >

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

Claim/purge disk space related to deleted files

Hi,


I deleted over 50GB of files from my computer (and had emptied the trash), since it was running out of disk space - however it seems that it did not actually freed that space since I am still getting the error saying the disk is full and it does not not allow me to save any file.


This is what I see when I look at the disk properties

User uploaded file


This is what currently shown in the Finder status bar

User uploaded file


What I've tried to far:

  1. Rebuilt the Spotlight index (How to rebuild the Spotlight index on your Mac - Apple Support)
  2. Ran First Aid tool using Disk Utility against the HD - all green there
  3. Reset NVRAM (How to reset NVRAM on your Mac - Apple Support) and SMC (How to reset the System Management Controller (SMC) on your Mac - Apple Support)
  4. Tried the process outlined on this page https://www.jackenhack.com/mac-os-purgeable-remove-clear-space

Would you please let me know how to claim that disk space (or manually force the disk purge)?


Thanks

Gilson

MacBook Air, macOS High Sierra (10.13.2)

Posted on Dec 14, 2017 4:18 AM

Reply
2 replies

Dec 14, 2017 2:59 PM in response to gosantos

I ran the First Aid on Safe mode and here is the output:

Verifying file system.

Volume could not be unmounted.

Using live mode.

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

Checking volume.

Checking the container superblock.

Checking the EFI jumpstart record.

Checking the space manager.

Checking the object map.

Checking the APFS volume superblock.

Checking the object map.

Checking the fsroot tree.

warning: fe_val: object (oid 0x2000003a0): invalid crypto_id (0x4)

warning: fe_val: object (oid 0x2000003a0): invalid crypto_id (0x4)

warning: fe_val: object (oid 0x2000bad14): invalid crypto_id (0x4)

warning: fe_val: object (oid 0x2000bb542): invalid crypto_id (0x4)

warning: fe_val: object (oid 0x2000bb7fd): invalid crypto_id (0x4)

warning: fe_val: object (oid 0x2000bb7fd): invalid crypto_id (0x4)

warning: fe_val: object (oid 0x2000bb7fd): invalid crypto_id (0x4)

warning: fe_val: object (oid 0x2000bb7fd): invalid crypto_id (0x4)

warning: fe_val: object (oid 0x2000bb7fd): invalid crypto_id (0x4)

warning: fe_val: object (oid 0x2000bb7fd): invalid crypto_id (0x4)

warning: fe_val: object (oid 0x2000bb7fd): invalid crypto_id (0x4)

warning: fe_val: object (oid 0x2000bb7fd): invalid crypto_id (0x4)

warning: fe_val: object (oid 0x2000bb7fd): invalid crypto_id (0x4)

warning: fe_val: object (oid 0x2000bb7fd): invalid crypto_id (0x4)

warning: fe_val: object (oid 0x2000bb7fd): invalid crypto_id (0x4)

warning: fe_val: object (oid 0x2000bb7fd): invalid crypto_id (0x4)

warning: fe_val: object (oid 0x2000bb7fd): invalid crypto_id (0x4)

warning: fe_val: object (oid 0x2000bb7fd): invalid crypto_id (0x4)

warning: fe_val: object (oid 0x2000bb7fd): invalid crypto_id (0x4)

warning: fe_val: object (oid 0x2000bb7fd): invalid crypto_id (0x4)

warning: fe_val: object (oid 0x2000bb7fd): invalid crypto_id (0x4)

warning: fe_val: object (oid 0x2000bb7fd): invalid crypto_id (0x4)

warning: fe_val: object (oid 0x2000bb82d): invalid crypto_id (0x4)

warning: fe_val: object (oid 0x2000bc80e): invalid crypto_id (0x4)

warning: fe_val: object (oid 0x2000bc817): invalid crypto_id (0x4)

warning: fe_val: object (oid 0x2000bc817): invalid crypto_id (0x4)

warning: fe_val: object (oid 0x2000bc817): invalid crypto_id (0x4)

warning: fe_val: object (oid 0x2000bc817): invalid crypto_id (0x4)

warning: fe_val: object (oid 0x2000bc817): invalid crypto_id (0x4)

warning: fe_val: object (oid 0x2000bc817): invalid crypto_id (0x4)

warning: fe_val: object (oid 0x2000bc817): invalid crypto_id (0x4)

warning: fe_val: object (oid 0x2000bc817): invalid crypto_id (0x4)

warning: fe_val: object (oid 0x2000bc817): invalid crypto_id (0x4)

warning: fe_val: object (oid 0x2000bc817): invalid crypto_id (0x4)

warning: fe_val: object (oid 0x2000bc817): invalid crypto_id (0x4)

warning: fe_val: object (oid 0x2000bc817): invalid crypto_id (0x4)

warning: fe_val: object (oid 0x2000bc817): invalid crypto_id (0x4)

warning: fe_val: object (oid 0x2000bc817): invalid crypto_id (0x4)

warning: fe_val: object (oid 0x2000bc817): invalid crypto_id (0x4)

warning: fe_val: object (oid 0x2000bc817): invalid crypto_id (0x4)

warning: fe_val: object (oid 0x2000bc817): invalid crypto_id (0x4)

warning: fe_val: object (oid 0x2000bc817): invalid crypto_id (0x4)

warning: fe_val: object (oid 0x2000bc817): invalid crypto_id (0x4)

warning: fe_val: object (oid 0x2000bc817): invalid crypto_id (0x4)

warning: fe_val: object (oid 0x2000bc817): invalid crypto_id (0x4)

warning: fe_val: object (oid 0x2000bc817): invalid crypto_id (0x4)

warning: fe_val: object (oid 0x2000bc817): invalid crypto_id (0x4)

warning: fe_val: object (oid 0x2000bc817): invalid crypto_id (0x4)

warning: fe_val: object (oid 0x2000bc817): invalid crypto_id (0x4)

warning: fe_val: object (oid 0x2000bc817): invalid crypto_id (0x4)

Checking the snapshot metadata tree.

Checking the extent ref tree.

Checking the snapshots.

Checking snapshot 1 of 1.

Verifying allocated space.

The volume /dev/rdisk1s1 appears to be OK.

File system check exit code is 0.

Restoring the original state found as mounted.

Operation successful.

I wonder if those warnings have something to do with the fact I still do not have any disk space left even though I have deleted ~50GB of files...


Any ideas?

Claim/purge disk space related to deleted files

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