Perfect, thanks. And I for the
ZFS slice at disk16s2, the ZEVO
zfs_pool_proxy might be disk17.
http://diigo.com/0u1wo for highlights from
Apple Fusion Drive—wait, what? How does this work? | Ars Technica (2012-10-23) … whilst Lee Hutchinson seems almost certain that implementation is
file-level, I am not certain of that.
As CoreStorage is for management of logical volumes – and as Patrick demonstrates a file system
without HFS Plus working with CoreStorage in ways that are
Fusion Drive-like – my assumption is:
If only a few blocks of a colossal file are used frequently, it will make sense for CoreStorage to:
- move only those few blocks (not the colossus) to the faster tier, to the faster physical volume(s).
Potential for confusionApple Fulfills Patent with the iMac's New Fusion Drive - Patently Apple (2012-10-23) – I don't think so. In
a 2011 article about Apple's patent application, Patently Apple observed: "… Apple's twist to this drive is that it will handle different types of storage media based on an environmental state of the hybrid drive. If the drive undergoes temperature, vibration or acceleration variances that could cause the hard drive to temporarily fail, the system would save the volatile data to the Flash drive …" and "… Apple's invention generally relates to a hybrid storage device that includes the following: a hard-disk drive (HDD), a flash memory, an interface circuit, and control logic. This control logic receives a request … from an external device to write a block of data to the hybrid … includes a logical address for the block of data in a first portion of an address space which maps to the HDD. In response to the request, the control logic writes the block of data to the HDD. … at least a portion of the block of data to a logical address for the block of data in a second portion of the address space which maps to the flash memory. …"
– I do
not see such things in Apple's Fusion Drive application of CoreStorage.