I seem to be having a lot of drama with this bug: https://bugs.launchpad.net/ubuntu/+s...a/+bug/1872476
I first noticed this bug when I upgraded a file server from 18.04 to 20.04 last month. During that time I installed new drives. The old drives shared fine, the new drive share is broken. Viewing from both Windows 10 machines and other a 20.04 machine shows files as folders, zero sized files, ect. Even more interesting if I copy those same files to a working share, it breaks there as well, but only those files. What really cook my noodle, take this example, share1 works, I copy a few files from share1 (where they work fine) to share2 on the server (not over SMB) and they fail when viewed over SMB (files and folders, zero size files). If copy the files from share2 to a new location on share1 they now fail on share1 even though all other files on share1 work, in fact the original files on share1 that I copied, work but not once they have been copied to the share that sometimes does not work. basically some shares work, others don't but even then some files work and some files don't in this case these were newer files but I did not look that hard, I have a real fear I will wipe out files by mistake.
To mitigate the issue I setup a second server with a clean 20.04 install. It's shares worked fine but needed more space, added another driver and boom, same bug. I know its not an SMB1 issue for me, I disabled it on the windows 10 machine and insured 2:4.11.6+dfsg-0ubuntu1.6 was installed and made sure SMB3 was is in use with smbstatus for both Ubuntu clients and Windows 10 clients. It seems confirmed in the notes that its a SMB3 issue as well however there has not been any movement I can see on the bug for several months now. It also works just fine on some drives but I can't figure out what specifically makes it work with some shares and not others. First thought was formatting/portioning. But I have working shares on exactly the same settings. Given this bug has effected 20.04 since it's launch and there are no pitchforks out I'm assuming there must be some workaround or some way to share that avoid the GIO issue. Or perhaps something I'm doing wrong when creating shares. Since 18.04 I have just used the built in create local share and let it set permissions.
Been struggling with this for a month now, several times I have spent hours googling but I just can't make it work over SMB3, any advice is welcome.
Adv Reply
Originally Posted by rsteinmetz70112
Bookmarks