Can you create an export with "admin user" and see if the issue is reproducible that way:
Mmsmb export add exportname /path/to/folder Mmsmb export change exportname -option "admin users=username@domain" And for good measure remove the SID of Domain Users from the ACL: mmsmb exportacl remove exportname --SID S-1-1-0 I can't quite think in my head how this will help but I'd be interested to know if you see similar behaviour. Richard -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Simon Thompson (Research Computing - IT Services) Sent: 19 December 2016 15:37 To: [email protected] Subject: [gpfsug-discuss] SMB issues Hi All, We upgraded to 4.2.2.0 last week as well as to gpfs.smb-4.4.6_gpfs_8-1.el7.x86_64.rpm from the 4.2.2.0 protocols bundle. We've since been getting random users reporting that they get access denied errors when trying to access folders. Some seem to work fine and others not, but it seems to vary and change by user (for example this morning, I could see all my folders fine, but later I could only see some). From my Mac connecting to the SMB shares, I could connect fine to the share, but couldn't list files in the folder (I guess this is what users were seeing from Windows as access denied). In the log.smbd, we are seeing errors such as this: [2016/12/19 15:20:40.649580, 0] ../source3/lib/sysquotas.c:457(sys_get_quota) sys_path_to_bdev() failed for path [FOLDERNAME_HERE]! Reverting to the previous version of SMB we were running (gpfs.smb-4.3.9_gpfs_21-1.el7.x86_64), the problems go away. Before I log a PMR, has anyone else seen this behaviour or have any suggestions? Thanks Simon _______________________________________________ gpfsug-discuss mailing list gpfsug-discuss at spectrumscale.org http://gpfsug.org/mailman/listinfo/gpfsug-discuss _______________________________________________ gpfsug-discuss mailing list gpfsug-discuss at spectrumscale.org http://gpfsug.org/mailman/listinfo/gpfsug-discuss
