3 ms·
I'm not a ZFS contributor or anything, but there's a lot of 'missing' features that would be nice but require moving or altering data that's stored on disk, so
by toast0 4y ago
I'm not a ZFS contributor or anything, but there's a lot of 'missing' features that would be nice but require moving or altering data that's stored on disk, so I think there's a general apprehension to that. ZFS is trying to be a lot of things, one of which is kind of archival quality storage; fiddling with things that were stored just fine on disk makes that harder to do.
A list of 'missing' features that need data moving off the top of my head: defrag (since we're talking about it), shrinking partitions (has some overlap with defrag), compression of existing data, dedup of existing data, moving data between filesystems on the same pool without having to read the data and write it a second time. I think there's maybe one other gotcha I can't remember.
All these things might be nice, but are tricky to get right, and users can figure out other ways to do them, so there you go. Limited resources and all.
- cryptonector 4y agoAdd to that list changing compression algorithms.
- rincebrain 4y agoThat one's only a little bad if you do it - you break uncompressed ARC with compressed L2ARC, nopwrite, and dedup, but all three of those are uncommon cases, and you can add helpful glue to make it work without breaking those with only a little work. For example, we've had three different zlibs compressing gzip streams for a while, and nobody really complained about it. (Linux ships 1.1.x; FBSD and everyone else ships 1.2.x; Intel QAT produces identical output to neither.) For a while, zstd was outputting different results on BE and LE systems and nobody noticed. Most of the reason we haven't updated compressors nowadays is that nobody's convinced anyone it's got enough benefit to be worth the added complexity.