[Samba] MacOS client suddenly can't open files
ml at netfence.it
Wed Mar 9 16:54:22 UTC 2022
I've got a strange report, which I didn't have the chance to fully
A MacOS Monterey user works with Samba shares (on FreeBSD + Samba
4.13.17), when suddenly she cannot open some specific files (which
change everytime): could be one specific file, could be all files in a
If she disconnects and reconnects again, the problem goes away.
If I rename one file server-side, then she can open it.
I tried smbstatus and it shows no lock on these files; the user says
she's the only one accessing them at that time.
(Altough I've seen locks pertaining to this users on a folder+file which
she says she didn't have open at that moment).
Has anyone seen something like this?
Is this a known problem?
Something obvious to look at/for?
bye & Thanks in advance
Relevant parts of smb.conf:
full_audit:success=all !closedir !connectpath !fdopendir
!openat !readdir !realpath !stat !telldir
full_audit:failure=all !get_real_filename !stat !translate_name
full_audit: prefix = IP=%I | USER=%u | MACHINE=%m | VOLUME=%S
shadow:sort = desc
kerberos method = secrets and keytab
idmap config *:backend = tdb
idmap config *:range = 100000-999999
idmap config XXXXXXXX:backend=rid
idmap config XXXXXXXX:range = 10000-99999
template homedir = /home/%U
winbind use default domain = yes
winbind refresh tickets = Yes
winbind expand groups = 4
winbind normalize names = Yes
domain master = no
local master = no
map acl inherit = Yes
store dos attributes = Yes
vfs objects=audit fruit streams_xattr recycle shadow_copy2
fruit:wipe_intentionally_left_blank_rfork = yes
fruit:delete_empty_adfiles = yes
fruit:metadata = stream
fruit:resource = xattr
fruit:nfs_aces = no
force create mode=660
force directory mode=770
More information about the samba