mount points for datasets "disappear" after replication
Description
Problem/Justification
None
Impact
None
SmartDraw Connector
Katalon Manual Tests (BETA)
Activity
Show:
Former user March 6, 2020 at 3:58 PM
I have experienced the same issue on 11.3-U1, on the pulling end of a replication.
Primary FreeNAS is replicated to secondary FreeNAS by pull, new replication method since 11.3 (Before that, was push from primary). All the replicated datasets are shown in the pool, but one of them ("homes") and sub-datasets are unmounted when replication starts.
Achim Staebler June 4, 2019 at 5:45 PM
Sorry, I was out on vacation. Debug info now available for both systems: nas (source of replication) and vault (target of replication)
Dru Lavigne May 28, 2019 at 11:30 AM
Achim: please attach a debug (System -> Advanced -> Save debug) to the Document Vault section of this ticket.
Need additional information
Pinned fields
Click on the next to a field label to start pinning.
Details
Details
More fields
Time tracking
More fields
Time trackingKatalon Platform
Linked Test Cases, Katalon Defect Results, Katalon Studio Test Results
Katalon Platform
Linked Test Cases, Katalon Defect Results, Katalon Studio Test Results
Created May 25, 2019 at 9:54 AM
Updated July 1, 2022 at 4:31 PM
Resolved June 4, 2019 at 3:24 PM
Following up on a request for help I posted in the forums:
I have set up a few replication task from a 9.10-U6 to another box which was then upgraded to 11.2-U4. The replication task is still running without errors after the upgrade but something weird is going on with the mount point. Let's take the dataset plexmediaserver_1 as an example:
It's listed as a dataset:
root@vault:/ # zfs list|grep plex
biggertank/jails/plexmediaserver_1 5.99G 26.2T 3.90G /mnt/biggertank/jails/plexmediaserver_1
It is mounted by zfs:
root@vault:/mnt/biggertank/jails # zfs mount | grep plex
biggertank/jails/plexmediaserver_1 /mnt/biggertank/jails/plexmediaserver_1
mount confirms:
root@vault:/ # mount|grep plex
biggertank/jails/plexmediaserver_1 on /mnt/biggertank/jails/plexmediaserver_1 (zfs, local, nfsv4acls)
However, the mount point does not exist at all:
root@vault:/ # ls -lad /mnt/biggertank/jails/plexmediaserver_1
ls: /mnt/biggertank/jails/plexmediaserver_1: No such file or directory
unmount and mount fixes this, but only until the next replication runs.
zfs umount biggertank/jails/plexmediaserver_1 && zfs mount biggertank/jails/plexmediaserver_1
My datasets and my pool are not read only, I confirmed this by zfs get all|grep readonly|grep -v off and by running zfs set readonly=off tank followed by a reboot.
This is getting slightly more annoying as it now affects my home dataset (which was previously not affected!), preventing users from logging in as the ssh keys are no longer "visible" on the box.
I am happy to provide more details, almost all of my datasets are now affected. and I can reproduce.
Here's the forum post for reference:
https://www.ixsystems.com/community/threads/empty-or-non-existent-mountpoint-after-zfs-replication.76160/#post-531791