After upgrading to 10.13, my 500GB SSD is nearly full. With 10.12 i always had ~200GB free. Looking at AboutThisMac->Storage->Manage, i see "System" using up nearly 300GB. However, looking at my SSD in finder, i cannot see any folders that would sum up to this size.
Does anyone notice this as well and is there a workaround?
radar://32782835
No, I meant "checking." APFS works as expected in reclaiming spaces in beta 2. I've tried quite some large files adding/deleting, disk space has been properly reclaimed 🙂
My experience to date is that APFS in Beta 2 does *not* exhibit this problem. I am keeping constantly refreshed backups via Carbon Copy Cloner and I still have my little magic USB installer becasue, well. you know.
However, since I reformstted and installed Beat 2, free space has remained around 55GB, so looking good so far
My experience too
Try deleting something large. This all started when my computer crashed. I'm wondering if my partition is somehow corrupted and APFS is unable to handle it. (Even though I can succesfully get through a First Aid.)
Beta 2 update 1 is still exhibiting this problem on my test machine. It's down to just over 3GB of free space with a System folder of over 130GB and growing every time I delete a file and empty the trash.
Bug report submitted!
Have you upgraded to APFS with Beta 2 Update 1 or before this release?
I think update doesn't fix problem if it already happened but prevents it to happen after installing.
Has anyone found a solution besides erasing and reinstalling? I noticed after Beta 2, my storage climbed a little bit.
I then tried installing public beta over it and since then, it has actually went down, probably because of the public download file but it looks like it was removed after the install.
If you do erase, can you restore from backup or do you need to start clean?
Anyone that is on Beta 2 after reinstalling, can you confirm your storage has not disappeared again?
First came here as my Time Machine 6TB volume in my Pegasus R4 array began having difficulties backing up my drives, which has never happened. I converted my volumes to APFS and made certain Time Machine is still HFS+ Journaled. Oddly, all APFS drives are greyed out and backing up is not working at all. Booted into safe mode, ran fsck on every volume, found some errors, made corrections, deleted an local snapshots (found two) and followed a number of suggestions from this thread (thanks!).
While reading I noticed the biggest issue is drive space being eaten away. Im sure this is not the problem but just in case, I had the very same issues on my current gen Mac Pro6,1 SSD. Turns out iCloud Drive was eating up my boot volume as "Store in iCloud" under "Storage" in "System Information" was turned on and was downloading files from my iTunes Library and Photos including any iCloud documents. I was panicking as GB's of data were disappearing in front of my eyes. Once I turned it off, all the space was freed and the amount of data returned to the usual range I am used to seeing.
Again, doubt this is the issue as it's too obvious and from what I gathered this goes deeper with issues between APFS and HFS+ (Journaled Extended) volumes. My issue is not being able to use any drive, my usual 6TB drive in my R4 array or any other attached drive formatted for Time Machine. It recognizes the volume, but under "Options" all of my hard drive including the boot drive that are now APFS are greyed out. If anyone has any advice I'd greatly appreciate it. Thanks!
Those steps saved my ass. Worked perfectly, and my restored CCC backup now shows the proper amount of free space on my internal drive.
After I had all the same issues of above, I did the following which solved all problems for me:
1. Made a backup with CCC
2. Removed my Samsung 850 EVO 1TB and did a Low Level Format on my Windows Server ( Low Level Format Tool)
3. Then formatted new HFS+
4. Replaced the SSD and booted with HIGH SIERRA DP1 Bootstick to do an absolut clean install.
5. After Configuration of iCloud, Apple ID and Networksettings updated Step by Step to DP 2.1. Enabling TRIM again.
6. Manually bring the files from Clone-backup back to the system
System was at about 18GB after this procedere and now during installations growing normally to 45GB. When I compare to my imac this seems to be correct. There it is at about 140GB..
There are no Backlight problems. Slow booting seems to be gone. System works very smooth without Fan overload.
The main problem I think is the conversion of the old used HFS+ to APFS and/or the enabled Trim.
When the work is over I will come back again and tell the last experiences belonging boot sequence time.
Only must get the machine MBP 13" late 2010 to active directory.
I had to deinstall Microsoft Office 2016. Aftre deleting the files, exactly 6,4 GB storage were freed from the SSD. Itb seem to work correct.
Booting time is reduced to 30-35 seconds. That is too long regarding 16-18 seconds before.
This is BETA code. It is FULL of debugging software. Longer boot times and degraded performance IS the normal in virtually 100% of beta builds.
Created and deleted a multi gigabyte file and all still seems to work as advertised - sort of. Space has not been below 51GB free since the reinstall, but now it's climbed to ^1Gb free (with 1.5GB purgeable), so the system's doing something behind the scenes. I know that APFS optmises for copies, but I don't have 10GB of copies.
Anyway, Beta 2 seems to work OK in this respect. If it matters, I'm on build 17A291m.
System is taking up 214GB on my 250GB SSD. Any luck on finding a workaround that doesn't involve wiping the drive? This also wasn't happening to me at first but seems to have appeared out of nowhere over the last few days.
have you used time machine?
tmutil listLocalSnapshotDates /
I believe I did.
This comes up blank for me when I enter it in terminal. Something is definitely being constantly created that is filling up the space though.
Did you try some third-party apps that help you figure out where the disk space is used? I've heard some mention the DaisyDisk app.
SInce I did as described above I have no problems anymore.
BUt do not use Time Machine.
there are no data created, only the disk is marked as used. Resulting of a time machine bug as I heard.
Volume snapshots are not meant to "create" new data. They are meant to mark existing data as "should save older version when something modifies this". Meaning, any changes you make after marking a new snapshot, are preserved by the Copy On Write behavior of the file system.
On 'macOS 10.13 Developer Beta 2 Release Notes', see Section 'Notes and Known Issues'
General
New Features
• Added AVRoutePickerView to the AVKit framework and AVRouteDetector to the AVFoundation framework for enabling users to choose the route for playing content when multiple routes are available. Use AVRouteDetector to determine if multiple routes are available when route detection is enabled. If multiple routes are available, use AVRoutePickerView to present an interface for the user to choose the routes. The functionality of AVRoutePickerView is disabled in this beta.
New Issues
• Resetting the NVRAM on a Mac with a bootable APFS partition prevents that partitionbeing used as the startup partition. (33013161, 32991435)
Workaround: Use Startup Manager to select the APFS partition as the boot partition. Toopen Startup Manager, hold the Option key immediately after rebooting the Mac.
• Time Machine is disabled for macOS High Sierra 10.13 beta 2 update 1 (17A291m). Apple recommends turning off Time Machine for APFS volumes on earlier versions of macOS 10.13 beta 2 as the space for snapshot files may not be freed correctly. (33006905)
Apple File System (APFS)
New Issues
• Encrypted APFS volumes can’t be decrypted. Decryption support will be added in an upcoming beta.
Resolved Issues
• Fixed an issue that prevented enabling FileVault on APFS volumes.
Known Issues
• Unsupported configurations in this seed release:
• HDD-only Macs currently are not converted to APFS by default.
• Some iMacs with 3TB Fusion drives and BootCamp may be unsupported for use with APFS.
• APFS support for Mid 2012 Mac Pro will be included in an upcoming seed.
• An APFS container on a Fusion drive can have only 1 macOS 10.13 volume.
• The encryption policy used for unencrypted APFS volumes that are converted to FileVault can cause the system to select the wrong block offset during the encryption process. This issue will be resolved in an upcoming beta, and will require the affected volumes to be reencrypted. Encrypted HFS+ volumes that have are converted to APFS are unaffected.
• There is a known issue where APFS systems with FileVault enabled cannot reset their password with iCloud.
• Resizing APFS containers is currently not supported in Disk Utility.
Workaround: In Terminal, use the diskutil tool to resize APFS containers.
• Some third-party applications may not correctly recognize volumes that are formatted using APFS.
Anyway, facing the same trouble here, was using Time Machine with Time Capusle for automatically back up. it seems no solution to purge the snapshots from the drive. I have the beta installed on my new MacBook Pro with SSD built-in as internal storage, I've deleted files total sized nearly 40GB, but only got 3GB back, it just drives me crazy as ****.
