[Samba] "No previous versions" - GPFS 3.5 and shadow_copy2
Sobey, Richard A
r.sobey at imperial.ac.uk
Wed Jul 6 13:13:04 UTC 2016
I forgot to add, my Samba version is sernet-samba-4.2.9, also tested 4.2.13 which has the same behaviour.
GPFS is 3.5.0.22.
Richard
-----Original Message-----
From: samba [mailto:samba-bounces at lists.samba.org] On Behalf Of Sobey, Richard A
Sent: 06 July 2016 13:29
To: samba <samba at lists.samba.org>
Subject: [Samba] "No previous versions" - GPFS 3.5 and shadow_copy2
Hi all,
At some point recently my customers can no longer see GPFS snapshots under the Windows Previous Versions tab. It simply says "No previous versions available". If a fileset is exported with the flag "force user = root" then Previous Versions *are* displayed.
[2016/07/06 10:07:35.602080, 3] ../source3/smbd/vfs.c:1322(check_reduced_name)
check_reduced_name: admin/ict/serviceoperations/slough_project/Slough_Layout reduced to /gpfs/prd/groupspace/ic/admin/ict/serviceoperations/slough_project/Slough_Layout
[2016/07/06 10:07:35.611881, 3] ../source3/smbd/dosmode.c:196(unix_mode)
unix_mode(admin/ict/serviceoperations/slough_project/Slough_Layout) returning 0644
[2016/07/06 10:07:35.613374, 0] ../source3/modules/vfs_shadow_copy2.c:1211(check_access_snapdir)
user does not have list permission on snapdir /gpfs/prd/groupspace/ic/admin/ict/.snapshots
[2016/07/06 10:07:35.613416, 0] ../source3/modules/vfs_shadow_copy2.c:1380(shadow_copy2_get_shadow_copy_data)
access denied on listing snapdir /gpfs/prd/groupspace/ic/admin/ict/.snapshots
[2016/07/06 10:07:35.613434, 0] ../source3/modules/vfs_default.c:1145(vfswrap_fsctl)
FSCTL_GET_SHADOW_COPY_DATA: connectpath /gpfs/prd/groupspace/ic, failed - NT_STATUS_ACCESS_DENIED.
[2016/07/06 10:07:47.648557, 3] ../source3/smbd/service.c:1138(close_cnum)
x.x.x.x (ipv4:x.x.x.x:51298) closed connection to service IPC$
That's a sample log excerpt from when I increased log level to 10 on a dev machine in the same cluster.
I cannot list permissions at all on the .snapshots folder, is this normal?
[root at server ict]# mmgetacl -k nfs4 .snapshots/
.snapshots/: Operation not permitted
There have been no changes made to our smb.conf recently, so we're extremely baffled why this should have suddenly broken.
Can someone please have a look at the smb.conf to see if any glaring mistakes are present, or suggest how I can troubleshoot the problem?
[global]
netbios name = store
workgroup = IC
security = ads
realm = IC.AC.UK
kerberos method = secrets and keytab
vfs objects = shadow_copy2 syncops gpfs fileid
ea support = yes
store dos attributes = yes
map readonly = no
map archive = no
map system = no
map hidden = no
unix extensions = no
allocation roundup size = 4096
disable netbios = yes
smb ports = 445
# server signing = mandatory
template shell = /bin/bash
interfaces = eth0 lo
allow trusted domains = no
printing = bsd
printcap name = /dev/null
load printers = no
disable spoolss = yes
idmap config IC : default = yes
idmap config IC : cache time = 180
idmap config IC : backend = ad
idmap config IC : schema_mode = rfc2307
idmap config IC : range = 500 - 2000000
idmap config * : range = 3000000 - 3500000
idmap config * : backend = tdb2
winbind refresh tickets = yes
winbind nss info = rfc2307
winbind use default domain = true
winbind offline logon = true
winbind separator = /
winbind enum users = true
winbind enum groups = true
winbind nested groups = yes
winbind expand groups = 2
clustering = yes
ctdbd socket = /tmp/ctdb.socket
gpfs:sharemodes = yes
gpfs:winattr = yes
gpfs:leases = yes
gpfs:dfreequota = yes
nfs4:mode = simple
nfs4:chown = yes
nfs4:acedup = merge
fileid:algorithm = fsname
force unknown acl user = yes
shadow:snapdir = .snapshots
shadow:fixinodes = yes
shadow:snapdirseverywhere = yes
shadow:sort = desc
syncops:onclose = no
syncops:onmeta = no
kernel oplocks = yes
level2 oplocks = yes
oplocks = yes
notify:inotify = no
wide links = no
async smb echo handler = yes
dmapi support = yes
aio write size = 1
aio read size = 1
socket options = IPTOS_LOWDELAY TCP_NODELAY
enable core files = no
#debug logging
log level = 10
log file = /var/log/samba.log.%m
max log size = 1024
debug timestamp = yes
[IC]
comment = Unified Group Space Area
path = /gpfs/prd/groupspace/ic
public = no
read only = no
valid users = "@domain users"
browseable = no
I'm investigating this on the GPFS list as well but it looks to me like the error lies with Samba, not GPFS.
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/options/samba
More information about the samba
mailing list