2018-01-24 13:41 GMT+01:00 Andreas Hasenack <andr...@canonical.com>: > Are all your shares on zfs? Or, more importantly, all shares where this > problem happens? > > all shares are on zfs
> Do you have it happening on shares where there are no vfs modules being > used? > > all shares use vfs modules > > Also, about my earlier question about the "id" command, I meant if the id > <user> command correctly resolves the groups *at the time* the problem is > happening, not in general. > yes i try id command at time of the problem and all groups were correctly resolved . Furthermore, access should not depend on the group since: 1) the owner of all files and folders is nobody 2) all shares use option force user nobody > > And lastly but not least, do you think you could disable the nss caching > for a while and see if the problem happens again? Or will that increase > the load too much on your systems? > It is a server in production that provides a truly critical file sharing service. If it stops, the analysis laboratories and the ambulatories of the entire hospital will stop. I do not feel like making such a change. Alberto -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1743354 Title: samba with backend ldap: can not access share or file even if user is authorized : NT_STATUS_ACCESS_DENIED To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1743354/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
