±Forensic Focus Partners

Become an advertising partner

±Your Account


Forgotten password/username?

Site Members:

New Today: 0 Overall: 36312
New Yesterday: 7 Visitors: 206

±Follow Forensic Focus

Forensic Focus Facebook PageForensic Focus on TwitterForensic Focus LinkedIn GroupForensic Focus YouTube Channel

RSS feeds: News Forums Articles

±Latest Articles

±Latest Videos

±Latest Jobs

Fusion HDD

Discussion of forensic workstations, write blockers, bridges, adapters, disk duplicators, storage etc. Strictly no advertising of commercial products, please.
Reply to topicReply to topic Printer Friendly Page
Forum FAQSearchView unanswered posts

Senior Member

Fusion HDD

Post Posted: Oct 26, 12 19:23

Anyone care to speculate on the impact that this piece of kit may have on our work?


Forensic Computer Analyst (LE)
BSc (Hons)

Senior Member

Re: Fusion HDD

Post Posted: Oct 30, 12 00:39

- neddy
Anyone care to speculate on the impact that this piece of kit may have on our work?

JFYI, only seemingly unrelated:

- In theory there is no difference between theory and practice, but in practice there is. - 

Senior Member

Re: Fusion HDD

Post Posted: Oct 30, 12 11:16

- neddy
Anyone care to speculate on the impact that this piece of kit ...

Just speculation: it looks like a unit that combines one HDD and one flash drive with added logic to move files/sectors from the one to the other depending on access frequency, and possibly more. That may make it remotely RAID-like in that it presents the standatd ATA interface to its host, but it is reasonably free to do whatever it likes on the inside.

Q1: How is the multiplexing between the HDD and the SSD done? Something like the P/G lists in HDDs? That is, when the host requests a sector N, the Fusion logic decides if that sector is present on the SSD, or if the request must be passed to the HDD. That would suggest that the SSD would be little but a container for 'fast' sectors' + some kind of sector access statistics database. (A bit like those 'Shadow' devices by ... was it Vogon?)

Q2: How many copies of sector N will there be? Two - one 'slow' on the HDD, and one 'fast' on the SSD? Or perhaps only one -- placed according to the access frequency? Two would be easiest to implement (just stuff the sector onto the SSD as it is being read), and probably safest in general. One would be rather messy to implement.

Q3: Q1 and Q2 assumes that this is a general purpose device, serving ATA protocol to the host, and doing access statistics on sectors. Is it? or is it a very special-purpose device that relies on the file system implementation to keep track of access patterns, and issuing orders to move files (or chunks of sectors) from the HDD to the SSD, or vice versa?

If this is a general purpose device, I suspect it will not pose any additional complexity -- the HDD will probably be the master copy. The SSD may contain old data, which could be useful in some contexts, say for files that are not version controlled.

If this is a special purpose device (i.e. heavily dependent on HFS+ implementation), it's as if an entirely new disk had appeared: non-ATA, non-SCSI, non-anything-else. That means starting from scratch as reagrds imaging as well as interpretation.

I'd suspect it's a general-purpose device, though -- it seems to make more sense from a business perspective than creating something very special only for Apple customers. On the other hand, those support answers suggest there is something special about it after all. But then again ... support is usually designed to minimize customer problems than to explain actual truth.  

Page 1 of 1