Thanks to aswink for the informative post, which confirms my suspicions as noted in my posts 15 and 17 above.
To "badlydrawnboy", the OP:
Again, my advice is:
If you want the problems you have to end, UN-fuse the fusion drive into separate SSD and HDD. It's not really that difficult to do.
If you're unwilling to do this, you will have to live with the problem until Apple acknowledges it and provides a fix.
There is also the possibility that it _cannot_ be "fixed" due to how fusion works (at the "block level" rather than the "file level", if my understanding is correct). This is unknown and remains to be determined.
Aside: I seem to recall from other posts on this board (where a user was trying to use the command line to create a fusion drive "manually") that something (exactly what is unknown) "changed" regarding fusion, from OS 10.8 to OS 10.9. Apple made some low-level tweak or adjustment to how fusion works. This may be the essence of the problems...
To "badlydrawnboy", the OP:
Again, my advice is:
If you want the problems you have to end, UN-fuse the fusion drive into separate SSD and HDD. It's not really that difficult to do.
If you're unwilling to do this, you will have to live with the problem until Apple acknowledges it and provides a fix.
There is also the possibility that it _cannot_ be "fixed" due to how fusion works (at the "block level" rather than the "file level", if my understanding is correct). This is unknown and remains to be determined.
Aside: I seem to recall from other posts on this board (where a user was trying to use the command line to create a fusion drive "manually") that something (exactly what is unknown) "changed" regarding fusion, from OS 10.8 to OS 10.9. Apple made some low-level tweak or adjustment to how fusion works. This may be the essence of the problems...
Last edited: