You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are sending our ZFS dataset to another server using ZREP and we noticed that the directory on the destination source does not get mounted automatically.
Setting zrep properties on data-source/files
Creating destination filesystem as separate step
Creating snapshot data-source/files@zrep_000000
Sending initial replication stream to hostname:data-destination/files
setting readonly on hostname:data-destination/files manually
Initialization copy of data-source/files to hostname:data-destination/files complete
Filesystem will not be mounted
Then I noticed that the zfs mount -a somehow makes it appear on the destination source, however on our other datasets using ZREP we did not have to manually run this command to make it appear.
We also used ZREP_CREATE_FLAGS="-o compression=lz4" instead but somehow it still inherits from the default data-set so we replaced it with ZREP_INIT_REMOTE_PROPERTIES.
We are using zrep v2.0.2 on the source server on Debian 12 (ZFS version 2.1.11).
Is this a recent change or is there something that we are missing?
The text was updated successfully, but these errors were encountered:
Hello,
We are sending our ZFS dataset to another server using ZREP and we noticed that the directory on the destination source does not get mounted automatically.
This is the output of the initial ZREP command:
Then I noticed that the
zfs mount -a
somehow makes it appear on the destination source, however on our other datasets using ZREP we did not have to manually run this command to make it appear.We also used
ZREP_CREATE_FLAGS="-o compression=lz4"
instead but somehow it still inherits from the default data-set so we replaced it withZREP_INIT_REMOTE_PROPERTIES
.We are using
zrep v2.0.2
on the source server on Debian 12 (ZFS version 2.1.11).Is this a recent change or is there something that we are missing?
The text was updated successfully, but these errors were encountered: