Let's assume I have an SSD that supports TRIM-supported drive, and I create a single encrypted partition that fills the entire disk (minus the obligatory GUID and recovery partitions). Is FileVault 2 smart enough to TRIM deleted bits, or does the full disk encryption prevent this from happening? Even if it does TRIM deleted bits, will the encryption of the full partition (presumably marking every bit in that partition as used) slow down the drive because there's nowhere clean left for it to write to, resulting in write amplification?

  • 1
    Why would TRIM even care what encoding is used to store the data. FV2 just scrambles the bits - not change the file allocation strategy or structure. The filesystem remains the same - so TRIM will succeed or fail based on FS - not encoding. Am I missing your point somehow?
    – bmike
    Commented Oct 7, 2011 at 20:07
  • 1
    TRIM depends on OS support. The question is whether Mac OS X will send the TRIM command if it using FileVault 2. It is possible that Apple's implementation of XTS-AES 128 does not bother to TRIM the bits it is overwriting.
    – lid
    Commented Oct 8, 2011 at 8:53

4 Answers 4


I guess I wasn't that convinced, so I tested this empirically.

Setup: MacBookPro6,2, Mac OS X 10.8.2, FileVault2 enabled, Crucial C300 256GB (firmware 0007)

With TRIM disabled, I nearly filled the disk (5 GB left) over the course of everyday usage. Deleting ~50 GB of files, I then tried to create a 50 GB disk image. Results were pretty pathetic - an initial peak at 180 MBps quickly dropping down to average writes of about 15 MBps, the disk clearly stuttering (showing periods of zero writes where presumably the disk was trying to catch up). The file was deleted, and afterwards I enabled TRIM. Again, I tried to create the disk image, and again I got the same results. Finally, after deleting the disk image, I created a disk image for the third time - with freshly TRIM'd bits. Average performance was 200 MBps and was sustained.

So no, FileVault2 does not interfere with TRIM. (And no, garbage collection is not sufficient, Crucial.)

  • We're using Sophos SafeGuard (ugh), I'll try to replicate this test with versions 5.50 and 6.02.
    – da4
    Commented Sep 25, 2012 at 15:30

TRIM support is not dependent on the encryption system you use. If your system supports TRIM and TRIM is activated then no matter how you store your data the low level IO operations will be handled by the system and will be not even know the difference between encrypted and unencrypted data.

So FileVault changes nothing at that level.

  • 1
    "low level IO operations will be handled by the system"... and FileVault 2 is part of the system, and is sufficiently low level that it could affect whether the TRIM command is being sent.
    – lid
    Commented Oct 8, 2011 at 8:58
  • @lid The difference between TRIM enabled operations and non TRIM operations is that the OS will notify the SSD about stale data at given adresses. Maybe your assumptions on FileVault 2 are incorrect. FileVault 2 works above the low level IO operations, also FileVault frees data on deletion (it doesn't encrypt empty disk space). So whenever an address space is freed wherever it's FileVault 2 enabled or not the OS will notify the SSD about stale data at the freed address and the TRIM operations will happen the same way they would without FileVault 2.
    – Coyote
    Commented Oct 1, 2015 at 8:49
  • I'm not making any assumptions about FileVault 2, hence the question. Could you provide a reference for your assertions? That would be much more convincing.
    – lid
    Commented Oct 1, 2015 at 9:11

I use FileVault 2 with TRIM enabled. It works without problems, but be aware that trimming out blocks make them zeroed out when read. This makes an attacker able to check how many blocks are written on the drive. This could lead to improved attacks.


Core Storage (aka using FileVault 2) operates above the level of TRIM storage handling so you won't negate the benefits of TRIM by enabling encryption.

TRIM speeds up reuse of deleted blocks on the storage. When the OS marks a block free, the SSD doesn't care if that block contained zeroes, ones or encrypted data. FileVault 2 doesn't change how many blocks get freed - just the pattern of what was left behind.

Before TRIM, the cleanup process suffers from write amplification - after trim commands are sent, that effect is minimized.

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .