- Sep 1, 2017
"Backward compatibility" means data created with older version of some software can be used by newer version of the same software.This is quite common.no it is not. what I expect (and ZFS does in most cases) is backwards compatibility.
"Backward compatibility" means data created with older version of some software can be used by newer version of the same software.This is quite common.
But what you expect is "forward compatibility": data created by newer version of software (in this case zfs 0.7) to be usable by older version of software (zfs 0.6.5)...
So you mean 0.6.5->0.7 is backward compatibility, and 0.7->0.6.5 is backward compatibility too? No offense, but maybe you could find some time to read those two wiki-links I posted, because you are mixing things terribly.
"Legacy mode" is again something quite different (as you can read on wiki too):
"...It (legacy mode) differs from backward compatibility in that an item in legacy mode will often sacrifice newer features or performance..."
OK, so let's close it so that you (ev. all Proxmox-team) call it "backward compatibility" (and I'll try to remember this peculiarity), but fortunately all other software-devs call it "legacy mode". Period.
This is not implemented as a feature flag, because the receiving side does not need to have implemented it to receive this stream; it is fully backwards compatible. We need a flag, though, because full send streams without it cannot necessarily be received as a clone correctly.