HistoricallyBefore ZEVO was transferred to GreenBytes, digital photography breakage was given – with screenshots – as a classic example of silent file corruption. I have archives/caches of some pages in the tenscomplement.com domain but not that page in particular.
Rewinding further, before the name ZEVO was given, here's a screenshot of part of a page that was cached for me by Diigo:

- Z-410 Storage, historical, extract.png (69.84 KiB) Viewed 459 times
In my opinion, the only point that was potentially misleading was
automatic repair of corrupted metadata. Depending on a person's interpretation of the word
metadata, the (then) beta of Z-410 might have been unable to repair automatically where a pool was limited to a
single disk. YMMV.
NowAs before ZEVO was released, there's the integrity that is associated with ZFS. In this forum I see no evidence of corruption with normal usage.
ZEVO aside for a moment, I recommend reading:
Back to ZEVO: I recently began experimenting with ungraceful removal of a cache device whilst a pool is online. Results to follow, in a separate topic.
From the guide to ZEVO:
ZEVO uses the standard ZFS on-disk format (v28) and is therefore binary compatible with ZFS on other platforms. However, direct interchange with other platforms is not supported in this version.
If you use the file system with any version 28-compatible OS, then decide to move
away from ZEVO for the same data on OS X:
- as things stand, that move will be away from ZFS.
As
zfs receive in general can not work with a
send from a more recent version, so the version (8?) currently used by MacZFS can not receive data sent by version 28 implementations such as ZEVO.
ZEVO Community Edition 1.1.1 fitness for your use case 12 GB memory is a good fit for
system requirements.
QuestionsWhat makes and models are the FireWire drives?
With your movies, might you use Final Cut X?