Hello everyone,
I’m facing a really strange problem with previous versions and TrueNAS on an iXsystem R20.
Since we changed the snapdir visiblity of the …/.zfs/ folder of a child dataset to visible we cannot see the previous versions in Windows. Even if we change it back to hidden like the other ones were previous versions are shown.
periodic snapshots were set at parent dataset recursively and work for all child datasets. Only the ones with SNAPDIR=visible do not show up in Windows previous versions, even after changing them back to hidden.
When I look at /var/log/samba4/log.smbd I can see the following error when tying to open the previous versions:
testparm -s shows the following

I do not know why the child datasets with snapdir=hidden lo longer show/export their snapshots to the Windows Previous versions while the other child data sets shows them.
Any Idea?
Best regards,
tbol.inq
What version of truenas is this? What is output of testparm -s
?
TrueNAS-13.0-U4
the output of testparm -s is:
# Global parameters
[global]
aio max threads = 2
bind interfaces only = Yes
client ldap sasl wrapping = seal
disable spoolss = Yes
dns proxy = No
domain master = No
enable web service discovery = Yes
interfaces = 127.0.0.1 10.100.8.54 10.110.4.61 10.110.101.41
kerberos method = secrets and keytab
kernel change notify = No
load printers = No
local master = No
logging = file
max log size = 5120
nsupdate command = /usr/local/bin/samba-nsupdate -g
preferred master = No
realm = GROUP.JENOPTIK.CORP
registry shares = Yes
restrict anonymous = 2
security = ADS
server min protocol = NT1
server multi channel support = No
server role = member server
server string = TrueNAS Storage Cluster sc-ixs-jen-11
template shell = /bin/sh
winbind cache time = 7200
winbind enum groups = Yes
winbind enum users = Yes
winbind max domain connections = 10
workgroup = GROUP
idmap config corp: range = 200000001-300000000
idmap config corp: backend = rid
idmap config *: range = 90000001-100000000
idmap config group: range = 100000001-200000000
idmap config group: backend = rid
rpc_server:mdssvc = disabled
rpc_daemon:mdssd = disabled
idmap config * : backend = tdb
directory name cache size = 0
dos filemode = Yes
force unknown acl user = Yes
vfs objects = shadow_copy_zfs
[v_cifs_jen_aps_001$]
comment = Root Share for xxx APS Data
ea support = No
kernel share modes = No
path = /mnt/pool0/v_cifs_jen_aps_001
posix locking = No
read only = No
smbd max xattr size = 2097152
vfs objects = shadow_copy_zfs ixnas zfs_core aio_fbsd
nfs4:chown = true
ixnas:dosattrib_xattr = false
[dfs-aps-jen$]
comment = DFS Share for xxx APS Data
ea support = No
kernel share modes = No
path = /mnt/pool0/v_cifs_jen_aps_001/dfs-aps-jen
posix locking = No
read only = No
smbd max xattr size = 2097152
vfs objects = shadow_copy_zfs ixnas zfs_core aio_fbsd
nfs4:chown = true
ixnas:dosattrib_xattr = false
I cannot get the point of the error…
When I open the exact same share and folder with the exact same user with the exact same permissions I see no previous versions in Windows Explorer, but when I open it via Total Commander then I see the previous versions. See here:
You have invalid auxiliary parameters is Services->SMB that are breaking your IPC$ share.
@awalkerix which one are invalid?
And where is the IPC$ share needed for previous versions?
The log spam about shadow copies on /tmp is because you set an invalid list of vfs objects in the global section of your SMB configuration.