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
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 ****.