Closed Harvie closed 2 years ago
I think it can be more difficult than that, because depending on zpool and zfs versions/format/features/(vendors)/... the sender and receiver might not have an agreeable compressed-data protocol, which is something an admin who sets stuff up can/should know, although scripts might test for (try to send a test blurb and compare the result, see if it errors out) but it may be impractical (delay, storage write-wear, ...) for doing upon every send or service startup.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
bump
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
bump
Dne 2021-08-27 21:57, stale[bot] napsal:
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
-- You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub [1], or unsubscribe [2].
Links:
[1] https://github.com/oetiker/znapzend/issues/424#issuecomment-907442230 [2] https://github.com/notifications/unsubscribe-auth/AACDQGG2YRIPNO3VG7QMWRTT67UZHANCNFSM4HKWIXSQ
-- S pozdravem Best regards Tomáš Mudruňka - Spoje.net / Arachne Labs
XMPP/Jabber: @.***
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
bump
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
I think that --features=compressed should be enabled by default if both pools are compressed. Maybe it's enough to check if DST is compressed, because if SRC is not compressed,
-c
will not work anyway...