5 ms·
Perhaps the reason is that ZFS is actually not a big win for Apple's core product market(1): laptops and single user workstations (even that is grudging). From
by iigs 17y ago
Perhaps the reason is that ZFS is actually not a big win for Apple's core product market(1): laptops and single user workstations (even that is grudging). From the original article:
Manage storage, not disks. You can put all your disks in a pool and specify the redundancy level. ZFS takes care of the rest.
Essentially all of Apple's products are single disk. There is virtually no win there.
No more silent data corruption.
The checksumming is a nice feature and desperately needed as disk capacity continues to explode but bit errors remain the same, but in practice probably the biggest risk is bugs in FS code:
http://www.techcrunch.com/2008/01/15/joyent-suffers-major-downtime-due-to-zfs-bug/ http://www.techcrunch.com/2008/01/15/joyent-suffers-major-do...
Easy snapshots.
This is slick and gives the UNIX guy in me happy dreams but Time Machine really stole the thunder on this for regular users. It's just easier to explain to an end user "go to your backup and drag the files back" instead of the way that snapshots work in ZFS.
High performance software RAID built-in.
Again, one disk devices can't benefit from this
Transparent compression on the fly.
I challenge anyone to come up with a big win for this for the common Mac case. Most common or data-intensive file formats are compressed because it's just easier for any computer to deal with.
(1) Considering Apple's server products, xSAN is actually very slick, and in a lot of cases the flexibility of SAN storage outweighs the benefits you would get from ZFS's multi-device integration. The JBOD model demonstrated by Thumper + ZFS can be incredibly inexpensive but doesn't align practically with many workloads, including (I would expect) the video processing business, which is probably Apple's biggest server market.
- spydez 17y agoEssentially all of Apple's products are single disk. There is virtually no win there. Well, if you're data-paranoid, like me, you can set your ZFS filesystem to keep 2 copies of every file on different parts of the disk. Then if your single disk has a sector or two go kaput, ZFS will notice the bad CRC on read and get the other copy. I've also heard of other improvements for single-disk, and SSD specifically, but alas, I can't find citations right now. Time Machine really stole the thunder on this for regular users. Time Machine's "snapshots" suck. Entirely new file every time a bit changes? Really? My 500 gig external disk just filled up. And it's only backing up a 250 GB drive. And I only started using Time Machine a few months ago. Virtual machines & TrueCrypt volumes that change often are a royal pain with TM. ZFS, on the other hand, can store 4 months worth of backups of a 1TB RAID array on my fileserver in way south of a gig. Also, ZFS send and ZFS recv are awesome ways to stream a filesystem snapshot over a network to, say, a Time Capsule. If you were so inclined.
- randallsquared 17y agoTime Machine's "snapshots" suck. Entirely new file every time a bit changes? Really? My 500 gig external disk just filled up. Yeah, this has been far less useful than I imagined it would be, just because it takes so much space for the backups.
- voidmain 17y agoActually, it's worse than that. Time machine's "snapshots" aren't snapshots - they don't represent a point in time at all. A time machine backup can complete and nevertheless be unrestorable. On filesystems that support snapshots - including Windows' - you can actually do a reliable backup, but not on OSX.
- igorhvr 17y ago> Essentially all of Apple's products are single disk. There is virtually no win there. You can have multiple copies even inside a single disk. And this is useful when you use cheap disks. > The checksumming is a nice feature and desperately needed as disk capacity continues to explode but bit errors remain the same, but in practice probably the biggest risk is bugs in FS code: This is not true. At some point, a heavily used disk will start failing. It is really nice to be protected against that - and very important to know when it starts happening. I talk from experience - I had a zpool scrub detect silent file corruption once. Curiously, it never happened again with that disk. But I keep using that disk (of course, with frequent backups) - and I would never do that (continue using a disk that failed) with any other Filesystem.
- chaostheory 17y agoAs spydez points out - ZFS does offer a major benefit for machines (laptops) running SSD: "[it evens] out write activity to avoid hot spot failures [in flash]." http://blogs.sun.com/jonathan/entry/not_a_flash_in_the http://blogs.sun.com/jonathan/entry/not_a_flash_in_the You also have to think about the possibilities that would have been possible with ZFS, like hybrid storage pools: efficient use of a Flash + Conventional HD setup http://blogs.sun.com/studler/entry/zfs_and_the_hybrid_storage http://blogs.sun.com/studler/entry/zfs_and_the_hybrid_storag...
- wmf 17y agoSSDs already wear level internally; ZFS makes no difference there. L2ARC would have been nice though.