I don't think disabling swapping is a good idea.
The Apple support page is quite unclear about this. It says that disabling time machine (unchecking automatic backup) deletes local snapshots, but it doesn't says whether doing so deactivates local backup.I thought TM stopped making snapshots when "back up automatically" is unchecked (ie manual mode).
It makes no sense that it would continue making local snapshots to me.
I see. Thanks for thatThe Apple support page is quite unclear about this. It says that disabling time machine (unchecking automatic backup) deletes local snapshots, but it doesn't says whether doing so deactivates local backup.
What eventually worked on my M1/Big Sur 11.3 Beta:
After the reboot, you could check that parameters worked by sysctl -a vm.compressor_mode, it should return 2 (no swap), instead of default 4.
- Boot into the recovery mode
- From the Terminal, Disable System Integrity Protection (SIP) via csrutil disable
- Add boot args NVRAM parameter for VM no-swap mode 2 using command :
nvram 40A0DDD2-77F8-4392-B4A3-1E7304206516:boot-args="vm_compressor=2"- Enable back SIP via csrutil enable
- reboot
My machine has automatic backups off, and lists no backups in the About This Mac Storage tab. Check yours.The Apple support page is quite unclear about this. It says that disabling time machine (unchecking automatic backup) deletes local snapshots, but it doesn't says whether doing so deactivates local backup.
That really depends. Yeah swap on would be better. But the current implementation is garbage.I don't think disabling swapping is a good idea.
After the reboot, you could check that parameters worked by sysctl -a vm.compressor_mode, it should return 2 (no swap), instead of default 4.
- Boot into the recovery mode
- From the Terminal, Disable System Integrity Protection (SIP) via csrutil disable
- Add boot args NVRAM parameter for VM no-swap mode 2 using command :
nvram 40A0DDD2-77F8-4392-B4A3-1E7304206516:boot-args="vm_compressor=2"- Enable back SIP via csrutil enable
- reboot
sudo nvram boot-args="vm_compressor=2"
My machine has automatic backups off, and lists no backups in the About This Mac Storage tab. Check yours.
I back up externally using time machine.
You can check how many local snapshots exist or are being created using sudo tmutil listlocalsnapshots /The Apple support page is quite unclear about this. It says that disabling time machine (unchecking automatic backup) deletes local snapshots, but it doesn't says whether doing so deactivates local backup.
You can check how many local snapshots exist or are being created using sudo tmutil listlocalsnapshots /
Delete them manually using sudo tmutil deletelocalsnapshots <date>. e.g. tmutil deletelocalsnapshots 2021-03-12-184729 or by disabling TM automatic backups
tmutil deletelocalsnapshots /
I have automatic backup enabled and I don't see backups listed in "About this Mac" nor in system profiler. I only see that the "other" category takes 256 GB, but I don't know if this includes the local snapshots.My machine has automatic backups off, and lists no backups in the About This Mac Storage tab. Check yours.
I back up externally using time machine.
Apparently, time machine is not supposed to do that if automatic backup is disabled. Have you checked with the following command ?I was in manual mode as well and still saw APFS snapshotting happening. Which I think was causing a lot of my writes.
sudo tmutil listlocalsnapshots /
They never acknowledge issues unless they cannot deny it any further or fear a lawsuit. I mean: They only care about one thing: Maximum profits. And issues could be bad press. In worst case you say "a very small percentage of users was affected by this very rare and harmless little issue".Apple is quite ridiculous. I have been checking this thread literally every single day to see if theres any update/fix/announcement from them. And no, nothing at all.
So what can I do? I have been postponing purchasing a MBA M1 for a very, very long time because of this SSD issue.They never acknowledge issues unless they cannot deny it any further or fear a lawsuit. I mean: They only care about one thing: Maximum profits. And issues could be bad press. In worst case you say "a very small percentage of users was affected by this very rare and harmless little issue".
Otherwise... they just they won't say anything and might silently fix it in the next release.
So what can I do? I have been postponing purchasing a MBA M1 for a very, very long time because of this SSD issue.
According to what you said, perhaps it is wiser for me to wait? But there is no telling how long I have to wait though, thats why...
Yes I am planning on getting the 16/512 MBA M1Well, I perfectly can understand that.
If you don't want to wait get 16GB and as large an SSD as you can afford.
That's what I did M1 Mac mini 16GB, 2TB.
That should serve me for at least a decade.
It's by far the best and cheapest Mac I ever bought over the last 30 years or so.
I have the 16/512 MBA M1 and don't have this issue or extreme TBW levels some people are experiencing. Hard to say how widespread it is but thankfully Im not affected. I didn't migrate however and started from scratch, only restoring documents / files from backups or cloud service so haven't ended up with any baggage the migration util might have missed or introduced. I've applied all BS upgrades and public beta's (11.3 Beta 3), rebuilt once and played around with disk benchmarks and running stupid workloads when I first got it - currently sitting at 4.16TBW since early Dec. and averaging 0.013 TBW per day with a fairly linear track putting me at around 10-13TBW per year based on current usage.Yes I am planning on getting the 16/512 MBA M1
So what can I do? I have been postponing purchasing a MBA M1 for a very, very long time because of this SSD issue.
According to what you said, perhaps it is wiser for me to wait? But there is no telling how long I have to wait though, thats why...
They are likely trying to figure out what is causing it. It isn't like the bad OS update that turned everybody's computer into a snail - only a small amount of people are having this issue. It could be Apple, it could be people trying to run too many programs for the ram they have, it could be certain programs causing the issue, or a mixture of several factors.Apple is quite ridiculous. I have been checking this thread literally every single day to see if theres any update/fix/announcement from them. And no, nothing at all.
Yeah, I have the 8 GB model and I had 4 TB written since December as well. Not overly concerned.I have the 16/512 MBA M1 and don't have this issue or extreme TBW levels some people are experiencing. Hard to say how widespread it is but thankfully Im not affected. I didn't migrate however and started from scratch, only restoring documents / files from backups or cloud service so haven't ended up with any baggage the migration util might have missed or introduced. I've applied all BS upgrades and public beta's (11.3 Beta 3), rebuilt once and played around with disk benchmarks and running stupid workloads when I first got it - currently sitting at 4.16TBW since early Dec. and averaging 0.013 TBW per day with a fairly linear track putting me at around 10-13TBW per year based on current usage.
So what can I do? I have been postponing purchasing a MBA M1 for a very, very long time because of this SSD issue.
According to what you said, perhaps it is wiser for me to wait? But there is no telling how long I have to wait though, thats why...
How can I check if I’m affected by this?