After Replication Dataset not visible via SMB Share on Windows PC

PeterB0256

Cadet
Joined
Apr 4, 2020
Messages
9
I need some help !
Not new to TrueNas but not a real specialist ( whoever it is ... ).

I searched really everything about this topic, found some useful hints, but finally
could not solve my problem.

Short discription:
I am using 2 TrueNAS Server ( both TrueNAS-12.0-U8 ).

On the TrueNAS Server 1 I have 2 datasets called "ZFS-DATENSICHERUNG" and "ZFS-FERNSEHER-FILME".

TrueNAS Server 2 I use for backing up the data from the first Server via Replication.

Replication Tasks are "PUSH" Tasks on Server 1.

Replication-01.jpg



After Replication succeeded it looks like this on the Target Server 2

Replication-02.jpg


So far, so good but ....

I activated 2 Windows SMB-Shares on the Target Server 2 to view the Data just replicated from Server 1

Replication-03.jpg


Both Shares are visible on the Windows System but only the first one "ZFS-DATENSICHERUNG" is accessible and files are visible, I can copy them and so on.
The second Share "ZFS-FERNSEHER-FILME" is not accessible until I set the dataset "readonly=false" and the permissions to "Full Control"
and even after this the Share is empty, means no files are visible via the SMB Share on the Windows machine !!!

The first share is still "readonly=true" and no permissions had to be changed and works just fine as it should be ....

If I look at the data on the Backup Server 2 via the TrueNAS Shell all data is in place and visible !!!!

What I am missing ???

Is this a permission issue I am not understanding - or is it a replication issue I am not understanding ???

I appreciate any help !!

Peter
 

PeterB0256

Cadet
Joined
Apr 4, 2020
Messages
9
That the dataset on the replication target is not mounted is very unlikely, because
the first replicated dataset is, as I said, visible and fully accessable.

And from the TrueNAS Shell on the target machine, the dataset is in place and everything is there -
means it is mounted on the machine !?

Any other ideas !?

Thank you !!
 

anodos

Sambassador
iXsystems
Joined
Mar 6, 2014
Messages
9,554
Okay. One step I often take when trying to understand permissions issues is to `su` to the user in question in an SSH session and check if path is accessible and whether I can stat the files. Two additional things that can go wrong with trying to access data on a replication target is:

1) id mismatches for users/groups between source and destination. "bob" on server 1 can have a different uid than "bob" on server 2. Ditto for groups. You can verify by running the command "id bob" and see the uid of the user, gid of primary group, and gids of additional groups.
2) the user may lack execute (x) permissions on one or more path component leading to the share in question. Execute on directories grants search/traverse rights through them. A simple combination of `su bob` then cd `local path` should give some idea about this.

A bonus alternative
3) you may not be authenticating to the server in question as the user you think you are (this can often happen if you have "guest" access enabled on the server). You can verify via 'midclt call smb.status AUTH_LOG | jq`
 

PeterB0256

Cadet
Joined
Apr 4, 2020
Messages
9
Thank you very much for the reply - will think and check about this !

Just to inform you - when logging in on the TrueNAS Target System from the Windows System
via "WinSCP" all data and files and folders are visible and accessable !!
 

PeterB0256

Cadet
Joined
Apr 4, 2020
Messages
9
Problem Solved !!!!

It has been an ACL Permission Issue on the Source Dataset !!!

I compared the 2 questionable Datasets on the Source machine and saw
that the working dataset on the Target machine had slightly different Permission
settings than the not working dataset !

Means, I set the permissions on the source correctly, deleted the target dataset on the backup server,
Replication starts again on Source Server and .... everything was fine !

Thanks for help !!!!
 
Top