mysqldump: got errno 22 on write - windows explorer locks up constantly

When I try to back up my SQL(mariadb) database using the following command: (I am issuing this command on my network drive in windows explorer ie: Z:\share\location)

mysqldump -u hedron -h darkstar -p

I get:

mysqldump: got errno 22 on write

This is after about 5 or 10 minutes of doing what appears to be nothing. If I issue the above command in my C:\ drive, it completes successfully.

Further, and this is my real problem, but there's no specific error messages, I get constant (and random) lock ups when browsing my samba share mount on a network drive.

I had searched for this issue, and some say it's caused by a confusion about how many files each system(windows and linux) can have open at the same time. I can't find the web page this solution was located, but I had put: "max open file = 16384" into smb.conf, but that was unsuccessful.

I'm convinced the issue is some sort of communication error between my Windows 10 64bit machine and my SarPI (Slackware64 raspberry pi) machine. I'm guessing my Windows ethernet card is misconfigured in some way. But I don't have the faintest clue what configuration setting to change or research.

So, what ethernet setting could be causing windows explorer to be locking up?

Well, I tried a different network adapter and that didn't help. I even tried fiddling with the settings and turning off offloading(as a tweak guide suggested), but that didn't make a difference.

The problem doesn't appear local to my Windows desktop, as my laptop was acting funny attached to the server as well. It could just be a bug in SARPI? But I would have no idea how to isolate where the problem is. I could use wireshark, but I would have no idea what to look for or even if that would be any help.

I saw this thread: https://www.linuxquestions.org/quest...es-4175638781/ And maybe I'm reading into it things that aren't there, but the issue seems similar in nature.

Is there someway to use wireshark or some other program either in windows or on my slackware samba server to discern what is going on?

A very brief network search says error 22 means there's not enough room for the backup file being created, or for the temporary file (which might be in a different place than the target file)

There's gigs and gigs of room for it to be created. 1.17TB according to Windows.

Does it work if you do the backup in Linux instead of in a Windows share?

I can only assume so. I can back it up to C:\ drive just fine. I just can't do it when I'm in network drive path. This could be a completely different problem, I'm just assuming it's caused by the same thing as the windows explorer locking up problem.

My network drive is Z:\ So, if I do:

Z:\backupdir>mysqldump -u hedron -h darkstar -p

I wind up with the error, but not if I issue it from C:\.