History Adapter - NAS Drive smb 3.1.1

[SCoe2k]

In the past I mounted my network drive via smb1. This worked perfectly and I could write all the history data to the mapped drive.

I changed to smb 3.1.1
I can reach the mapped drive via ssh and for example backup Adapter can write on NAS.
History adapter will not write on NAS. It creates the folder of the day and creates only ZERO byte files. The error log states read/write errors.
Any idea? Is history able to read/write from mounted smb 3 drives?

Mounting via fstab:
//192.168.1.1/Luftiger-SG/4TB_HDD_SG/Smarthome/iobroker/Data /media/Luftiger_iobroker_Data cifs credentials=/home/pi/.smbcredentials,vers=3.1.1,uid=1000,gid=1000,rw,dir_mode=0777,file_mode=0777,x-systemd.automount,x-systemd.requires=network-online.target 0 0

[Apollon77]

is the iobroker user allowed to write and read there?
In fact the history adapter uses normal file operations to read/write and so it is unimportant if samba or nfs or direct hdd/ssd ...

[SCoe2k]

I am not an expert, but my understanding is that with privileges 0777 everyone is allowed to read and write.

[Apollon77]

Sollte, ja. Gibt es in /var/log/syslog weitere Infos?

[SCoe2k]

Folgende Infos sind in der syslog zum Zeitpunkt der Schreibversuche:

Aug 7 10:40:33 raspi04 kernel: [27619.393220] cifs_all_info_to_fattr: 15 callbacks suppressed
Aug 7 10:40:33 raspi04 kernel: [27619.393223] CIFS VFS: bogus file nlink value 0
Aug 7 10:40:33 raspi04 kernel: [27619.406102] CIFS VFS: bogus file nlink value 0
Aug 7 10:40:33 raspi04 kernel: [27619.440048] CIFS VFS: bogus file nlink value 0
Aug 7 10:40:33 raspi04 kernel: [27619.492926] CIFS VFS: bogus file nlink value 0
Aug 7 10:40:33 raspi04 kernel: [27619.526104] CIFS VFS: bogus file nlink value 0
Aug 7 10:40:33 raspi04 kernel: [27619.560360] CIFS VFS: bogus file nlink value 0
Aug 7 10:40:33 raspi04 kernel: [27619.620848] CIFS VFS: bogus file nlink value 0
Aug 7 10:40:33 raspi04 kernel: [27619.663128] CIFS VFS: bogus file nlink value 0
Aug 7 10:40:33 raspi04 kernel: [27619.676561] CIFS VFS: bogus file nlink value 0
Aug 7 10:40:33 raspi04 kernel: [27619.714122] CIFS VFS: bogus file nlink value 0

Related iobroker log:

2020-08-07 10:40:33.599 - error: history.0 (20740) Cannot read file /media/Luftiger_iobroker_Data/History/20200807/history.fritzdect.0.Comet_119610836272.temp.json: Error: UNKNOWN: unknown error, open '/media/Luftiger_iobroker_Data/History/20200807/history.fritzdect.0.Comet_119610836272.temp.json'
2020-08-07 10:40:33.737 - error: history.0 (20740) Cannot store file /media/Luftiger_iobroker_Data/History/20200807/history.fritzdect.0.Comet_119610836272.temp.json: Error: UNKNOWN: unknown error, open '/media/Luftiger_iobroker_Data/History/20200807/history.fritzdect.0.Comet_119610836272.temp.json'
2020-08-07 10:40:33.880 - error: history.0 (20740) Cannot read file /media/Luftiger_iobroker_Data/History/20200807/history.fritzdect.0.Comet_119610660352.temp.json: Error: UNKNOWN: unknown error, open '/media/Luftiger_iobroker_Data/History/20200807/history.fritzdect.0.Comet_119610660352.temp.json'

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs within the next 7 days. Please check if the issue is still relevant in the most current version of the adapter and tell us. Also check that all relevant details, logs and reproduction steps are included and update them if needed. Thank you for your contributions.
Dieses Problem wurde automatisch als veraltet markiert, da es in letzter Zeit keine Aktivitäten gab. Es wird geschlossen, wenn nicht innerhalb der nächsten 7 Tage weitere Aktivitäten stattfinden. Bitte überprüft, ob das Problem auch in der aktuellsten Version des Adapters noch relevant ist, und teilt uns dies mit. Überprüft auch, ob alle relevanten Details, Logs und Reproduktionsschritte enthalten sind bzw. aktualisiert diese. Vielen Dank für Eure Unterstützung.

[stale]

This issue has been automatically closed because of inactivity. Please open a new issue if still relevant and make sure to include all relevant details, logs and reproduction steps. Thank you for your contributions.
Dieses Problem wurde aufgrund von Inaktivität automatisch geschlossen. Bitte öffnet ein neues Issue, falls dies noch relevant ist und stellt sicher das alle relevanten Details, Logs und Reproduktionsschritte enthalten sind. Vielen Dank für Eure Unterstützung.