Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ZREP - Filesystem will not be mounted #202

Open
CamZie opened this issue Aug 4, 2023 · 1 comment
Open

ZREP - Filesystem will not be mounted #202

CamZie opened this issue Aug 4, 2023 · 1 comment

Comments

@CamZie
Copy link

CamZie commented Aug 4, 2023

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.

ZREP_INIT_REMOTE_PROPERTIES="compression=lz4" zrep init data-source/files hostname data-destination/files

This is the output of the initial ZREP command:

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?

@ppbrown
Copy link
Member

ppbrown commented Aug 5, 2023

Hello,
this is something that probably has nothing to do with zrep itself, but I'll give you my best guess:

I recall that there are certain option at the filesystem level and/or the OS level, that can be set, that affect automounting.

You may have somehow removed the automount magical property on the filesystem replica on that one system.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants