- Joined
- Jan 8, 2013
- Messages
- 138
- Motherboard
- Gigabyte Z370M-D3H
- CPU
- i5-8600K
- Graphics
- RX 570
- Mac
- Mobile Phone
I see some people here saying they don't "trust" APFS and are going through increasingly convoluted processes to continue using a 20 year old file system that isn't officially supported under the latest OS. What, exactly, is not "trusted" about it? I'm having difficulties finding any verifiable cases of any data loss or other filesystem issues on any revision of APFS even remotely associated with Mojave. Back in the version that released with High Sierra, Mike Bombich (of CCC fame) found a single bug with DiskImagesHelper that related to handling of sparse images (and only specifically triggered in odd edge cases, and only specifically when moving data into a sparse image), but that bug was reported and fixed quite some time ago. I guess I'm just curious why people are going so far out of their way to avoid using what Apple is extremely strongly recommending all macOS users use.
My only issue with APFS is the slow boot time when TRIM is enabled. I have a samsung 960 EVO nVME SSD and it takes 2x time to boot than from a standard HFS+ HDD. Trim on NVMe is different (not affected by trimforce) than SATA TRIM. After the boot process it's blazing fast, the slowness is only at the boot phase.
"I think there may be a problem with TRIM and non-Apple SSDs, and there are even reports of problems with Apple SSDs [and likely related to TRIM]" - see this thread.
Last edited: