To view parent comment, click here.
To read all comments associated with this story, please click here.
Wouldn't Time Machine profit greatly speed-wise from ZFS
Sure, but just that - speedups (which could probably be hacked around in many ways). I think Apple would want to go beyond of all that - like presenting to applications something else that a path and a stream of bytes.
With the same hardware, the only way to achieve ZFS like speeds for snapshots, is to adopt zfs like methods. Waving you hand and using the word hack doesn't change that. Apple probably wants ZFS like features ( for teh speed and reliability) but use it like HFS+ with the psuedo BFS features and legacy Mac-isims.
But that would take a lot of work, and frankly apple doesn't give a crap about painless effortless snapshots, so no ZFS. They'd rather have something that took forever, but was easy to use, than something instantaneous but had a more difficult UI.
In my never-humble opinion, I think you pretty much wouldn't want to present application developers with a representation of a file that was much more complicated than a path and a stream of bytes. I doubt most application developers want much more than that from a file; for them, neat new features are just added complexity.
The stream-of-bytes-at-a-path model of a file has lived for so long and changed so little because it's a good model that works very well for its intended purpose. It's not likely that someone's going to come up with some new-and-better metaphor for permanently-stored data on a disk, that's going to supplant the filesystems of today.
Edited 2009-10-26 19:23 UTC






Member since:
2007-06-22
Wouldn't Time Machine profit greatly speed-wise from ZFS if only the changed blocks between two snapshots would have to be sent to the backup disks instead of whole files (which is especially painful with large ones)? I do not own a Time Capsule but I read that larger backups can be quite painful over the air. Plus, the sometimes long calculation of the changes would also disappear.