Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

MP 7,1 Big Sur <> trimforce???

cobra521

cobra521

macrumors 6502
Original poster
Dec 14, 2016
393
136
FL
I have a 7,1 2019 Mac pro with macOs Big Sur 11.1. with 8 PCIe SSDs on Sonnet cards. Some of the SSDs are Samsung 970 Evo plus, and some are HP EX950s.

I've just enabled trimforce in Terminal.

Have I made a misteak:eek:??? Should I turn it off?

Tom
 
Why?

Because there seem to be opinions regarding lengthening/shortening the life of an NVME SSD, or possibly inviting data corruption according to the Apple disclaimer that pops up when you enable trimforce.

Tom
 
cobra521 said:
Why?

Because there seem to be opinions regarding lengthening/shortening the life of an NVME SSD, or possibly inviting data corruption according to the Apple disclaimer that pops up when you enable trimforce.

Tom
Click to expand...
If you don't turn it on, then the SSD's life span will be shorten. So, turn on TRIM can't be the mistake.

"TRIM may cause data lost" is an old problem on Linux, not macOS. And that's many years ago. However, since that happened before, and Apple has no way to make sure all 3rd party SSD can work flawlessly with TRIM. Therefore, they have to show you that disclaimer.

Anyway, they have lots of similar disclaimer for other functions (e.g. iCloud), apparently, we generally won't considered that we have to avoid any function (including TRIM) even Apple's disclaimer show us what the possible risks are.

Therefore, I can't see why "enable TRIM" can be a mistake.
 
  • Like
Reactions: yurc and OkiRun
All Trim does it provide an updated free list to the SSD, which makes its garbage collection more efficient. It does not have to wait for a sector write request.
Without trim the SSD firmware can only rely on blocks requested to be written to be garbage collected. It will add them to the free list and then write to an erased block. Not a big deal for disks <80% full, but nearly full drives will suffer slower writes with large files. With trim all free blocks are known and can be reclaimed in the background during idle time.
 
  • Like
Reactions: Basic75
Cindori is a very trustable developer.

Since the TrimEnabler official page says TrimEnabler 4 is supported. Then I will assume it’s safe to use.

By the way, TRIM should be enabled by default for NVMe. I have no idea how you RAID the NVMe, but if TRIM can’t be used in that RAID array, then I don’t think TE4 can’t help. You may consult Cindori to confirm that.
 
  • Like
Reactions: choreo
I had the notion that Apple's APFS took care of this function already?

Also checking my NVMe connected internal drives for both Apple and all the Samsung sticks, I see that TRIM Support is already indicated as "Yes".

What am I missing?

Screen Shot 2021-01-14 at 9.38.21 PM.png
 
h9826790 said:
Nothing about APFS, NVMe has TRIM enabled in MacOS by default
Click to expand...
Thanks for clarification. I meant APFS was created to handle NVMe drives and works better with TRIM and therefore would have been enabled by the OS from the get go without further manual enabling.
 
LeonPro said:
Thanks for clarification. I meant APFS was created to handle NVMe drives and works better with TRIM and therefore would have been enabled by the OS from the get go without further manual enabling.
Click to expand...
I am not sure about that.

But I believe APFS is designed for high performance solid state storage, not just NVMe.

And I think even with HFS+, macOS still enable TRIM for NVMe by default.

On the other hand, all other non NVMe SSD also work better with TRIM, but macOS default to disable TRIM for all of them.

I really don't know the logic behind, there is no consistence (except NVMe have everything).
 
  • Like
Reactions: LeonPro
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back