[Samba] delayed write files errors
rpenny at samba.org
Tue Jan 7 17:27:42 UTC 2020
On 07/01/2020 16:32, Ni Co wrote:
> Le 05/01/2020 à 14:27, Rowland penny via samba a écrit :
>> On 05/01/2020 11:36, Ni Co wrote:
>>> Hello Rowloand,
>>> ok, I just keep "default" for the mounting.
>>> I changed the path of my share :
>>> comment = User Home Folder
>>> path = /home/%U
>>> read only = no
>>> follow symlinks = yes
>>> wide links = yes
>>> browseable = no
>>> hide files = /desktop.ini/$RECYCLE.BIN/
>> You were using a share called '[users]' where a 'path' parameter is
>> required, but you have now changed it to '[homes]'. This is a special
>> share and does not allow the use of the 'path' parameter.
> However, the use of [homes] works correctly. But ok, I changed the name
> of the share as you advise me.
>>> Anyway, I still get the same error with all this files :
>>> mrxsmb :
>> By the backslashes, this appears to be coming from windows, so is
>> there an event ID ?
> Yes it's a Windows Event, mrxsmb, ID 139. Strangely it's always for
> *sqlite-shm files.
This looks like a Windows problem and not a Samba problem
>>> Also, I can see the file favicons.sqlite-shm in the samba log (@
>>> [2020/01/04 23:59:55.709000, 2]) with som errors.
>> What is the full log fragment ? The lines around the error.
> It was in the log file in my previous email (level log file = 3) :
> [2020/01/04 23:59:55.709000, 2] ../source3/smbd/open.c:1447(open_file)
> EXAMPLE\myuser opened file
> .system/Thunderbird/profile-release/favicons.sqlite-shm read=No write=No
> [2020/01/04 23:59:55.709255, 3]
> smbd_smb2_request_error_ex: smbd_smb2_request_error_ex: idx
> status[NT_STATUS_INVALID_INFO_CLASS] || at
> [2020/01/04 23:59:55.714015, 2]
> EXAMPLE\myuser closed file
> .system/Thunderbird/profile-release/favicons.sqlite-shm (numopen=13)
> On the other hand, is this error normal ?
> [2020/01/04 23:59:55.719198, 3]
> Found account name from PAC: MYPC$ 
> [2020/01/04 23:59:55.719241, 3]
> Kerberos ticket principal name is [MYPC$@EXAMPLE.DOMAIN.FR]
> [2020/01/04 23:59:55.721193, 3]
> get_user_from_kerberos_info: Username EXAMPLE\MYPC$ is invalid on
> this system
A computer is a special kind of user, so it sort of makes sense it is
invalid on a Unix system, so I wouldn't worry about it.
More information about the samba