#10 I/O Exceptions with Windows shares from version 0.6.1

[Elke Hofmann]

There seems to be some problem in version 0.6.1 working with windows server shares:
accessing windows shares (inside a VM with debian 10 server, Windows Server 2019 with a share, Windows 10 with a server, or in the future productive network from my Linux Mint 20 client to two remote windows shares) causes the following problem:
all things very slow
echo text > file -> if file exists, fine, if not exists I/O exception and empty file created
echo text >> file -> always I/O exception

I also have two debian 9 servers with smbnetfs 0.6.0 -> all things work perfectly!

Also to mention that mounts work fine with cifs in ALL Settings so this issue cannot be a question of privileges.
As our servers shall be upgraded to debian buster soon, so any help would be appreciated.
Thank you very much in advance.

[Mikhail Kshevetskiy]

try 0.6.2, probably the problem was fixed

[Elke Hofmann]

[Elke Hofmann]

[Mikhail Kshevetskiy]

Here is the recommendation from the ENGLISH.FAQ

Q5: I have a problem, what should I do ?

A5: It's quite often that the cause of errors is the samba and/or SMBNetFS
misconfiguration. To understand the cause of the error, set the value of
“smbnetfs_debug” to 5, 6 or 7 (also it maybe useful to setup
“smb_query_browsers” to false) and run “smbnetfs” with an additional
option "-d". Repeat your steps to reproduce the error. Examine the debug
information and try to fix the error by yourself. If it does not help,
try to contact with the author (please do not forget the debug output).

Examples of collecting debug  information:

smbnetfs -d -o smbnetfs_debug=7 mountpoint | tee -o smbnetfs.log
smbnetfs -d -o smbnetfs_debug=7,smb_query_browsers=false mountpoint | tee -o smbnetfs.log

[Elke Hofmann]

[Mikhail Kshevetskiy]

This output is not full. It seems to me you miss '-d' option so smbnetfs become a daemon process and the rest of output was not printed.

what I need (in short)
1) enable debug output
2) do actions to get an error
3) send me whole debug output (better with the commands from step 2) by email (the output will be quite large

There are 2 ways to enable debug output
1) run smbnetfs with options
smbnetfs -d -o smbnetfs_debug=7 mountpoint | tee -o smbnetfs.log
smbnetfs -d -o smbnetfs_debug=7,smb_query_browsers=false mountpoint | tee -o smbnetfs.log
2) set debug output in smbnetfs config ~/.smb/smbnetfs.conf (parameters "smbnetfs_debug" and "log_file")
The first is preferred as it enable the fuse debugging messages as well.

It's better to provide 8 different logs
a) debian 9 + "echo text > file" if file is not exist
b) debian 9 + "echo text > file" if file is exist already
c) debian 9 + "echo text >> file" if file is not exist
d) debian 9 + "echo text > file" if file is exist already
and the similar for debian 10

PS: smbclient utility does not use libsmbclient library, so it works in a different manner :-(

[Elke Hofmann]