Can't copy from Samba shares after upgrade to 18.04











up vote
2
down vote

favorite












A server "S" runs Ubuntu 18.04 LTS and Samba 4.7.6-Ubuntu. smb.conf has been left with all the default settings, except for workgroup name changed, and the following blocks added at the bottom:



[lan_share]
path = /disk2
browseable = yes
read only = yes

[lan_share_1]
path = /disk1
browseable = yes
read only = yes

[lan_share_3]
path = /disk3
browseable = yes
read only = yes


When the client was Debian 8 with packages samba and 'cifs-utils`, everything worked as expected, including ability to copy from the client-mounted share to local disks.



Now new client, workstation "W", is running Ubuntu 18.04 LTS with the latest samba and cifs-utils, and copying from shares to local is not working.



The shares on W are set up by lines in /etc/fstab as follows:



//192.168.1.233/lan_share_1 /disk1     cifs  credentials=/etc/samba/user,noexec  0 0
//192.168.1.233/lan_share /disk2 cifs credentials=/etc/samba/user,noexec 0 0
//192.168.1.233/lan_share_3 /disk3 cifs credentials=/etc/samba/user,noexec 0 0


There's a credentials file at the path listed above which, again, works fine with Debian, and probably is OK on Ubuntu too, as there are no error messages about permissions.



All this has been copied exactly from the Debian client which had no problem. Now an attempt to copy a directory tree thru the GUI file browser - say, from /disk2 to home directory - will appear to succeed at first, then the progress dialog freezes partway thru and can't even be cancelled. The progress dialog remains until the Thunar (file browser) process is killed - unless the user clicks the big red "Cancel" icon, in that case the dialog says "Cancelling..." until the process is killed. Only the first few files get copied.



I've checked that:




  • workgroup name is the same on both server and client

  • ufw on the server allows the ports in "samba" application profile

  • files in the share are OK on the server (accessible via SSH, SCP)

  • everything else works correctly on the client


I still have the Debian system where everything works normally when connecting to the same share - a whole directory structure can be copied from the share to local thru the GUI. Web searching has found various other Samba issues, some relating to going from earlier versions to Ubuntu 18, but none quite describing this situation.



Update: This ("Trouble mounting cifs shares after upgrade to 17.10") looked promising. I found out the "noexec" is unnecessary (1) and based on the former page, I replaced the ",noexec" with ",vers=2.1".



Also, on the server, did this: sudo chmod-R 775 /disk2. And with one or both of these changes in place, I can now successfully copy from the locally mounted share to home directory using command line - but it still makes Thunar hang. Now thinking it may be at least partially a GUI problem.



Update: Thanks Terrance, I'm going to check out NFS right away. I don't have Windows clients and if it's less problematic, well I just need the functionality.










share|improve this question
























  • +1 for a great question. Unfortunately, I have not stumbled across your issue with my network, but there were some issues I did have with cifs. Mostly cosmetics like incorrect used space reporting from server side. askubuntu.com/questions/1058815/… I ended up going with NFS on the server side but kept Samba as well. The speed on the NFS is faster and I get the correct used space reporting.
    – Terrance
    Nov 8 at 15:13

















up vote
2
down vote

favorite












A server "S" runs Ubuntu 18.04 LTS and Samba 4.7.6-Ubuntu. smb.conf has been left with all the default settings, except for workgroup name changed, and the following blocks added at the bottom:



[lan_share]
path = /disk2
browseable = yes
read only = yes

[lan_share_1]
path = /disk1
browseable = yes
read only = yes

[lan_share_3]
path = /disk3
browseable = yes
read only = yes


When the client was Debian 8 with packages samba and 'cifs-utils`, everything worked as expected, including ability to copy from the client-mounted share to local disks.



Now new client, workstation "W", is running Ubuntu 18.04 LTS with the latest samba and cifs-utils, and copying from shares to local is not working.



The shares on W are set up by lines in /etc/fstab as follows:



//192.168.1.233/lan_share_1 /disk1     cifs  credentials=/etc/samba/user,noexec  0 0
//192.168.1.233/lan_share /disk2 cifs credentials=/etc/samba/user,noexec 0 0
//192.168.1.233/lan_share_3 /disk3 cifs credentials=/etc/samba/user,noexec 0 0


There's a credentials file at the path listed above which, again, works fine with Debian, and probably is OK on Ubuntu too, as there are no error messages about permissions.



All this has been copied exactly from the Debian client which had no problem. Now an attempt to copy a directory tree thru the GUI file browser - say, from /disk2 to home directory - will appear to succeed at first, then the progress dialog freezes partway thru and can't even be cancelled. The progress dialog remains until the Thunar (file browser) process is killed - unless the user clicks the big red "Cancel" icon, in that case the dialog says "Cancelling..." until the process is killed. Only the first few files get copied.



I've checked that:




  • workgroup name is the same on both server and client

  • ufw on the server allows the ports in "samba" application profile

  • files in the share are OK on the server (accessible via SSH, SCP)

  • everything else works correctly on the client


I still have the Debian system where everything works normally when connecting to the same share - a whole directory structure can be copied from the share to local thru the GUI. Web searching has found various other Samba issues, some relating to going from earlier versions to Ubuntu 18, but none quite describing this situation.



Update: This ("Trouble mounting cifs shares after upgrade to 17.10") looked promising. I found out the "noexec" is unnecessary (1) and based on the former page, I replaced the ",noexec" with ",vers=2.1".



Also, on the server, did this: sudo chmod-R 775 /disk2. And with one or both of these changes in place, I can now successfully copy from the locally mounted share to home directory using command line - but it still makes Thunar hang. Now thinking it may be at least partially a GUI problem.



Update: Thanks Terrance, I'm going to check out NFS right away. I don't have Windows clients and if it's less problematic, well I just need the functionality.










share|improve this question
























  • +1 for a great question. Unfortunately, I have not stumbled across your issue with my network, but there were some issues I did have with cifs. Mostly cosmetics like incorrect used space reporting from server side. askubuntu.com/questions/1058815/… I ended up going with NFS on the server side but kept Samba as well. The speed on the NFS is faster and I get the correct used space reporting.
    – Terrance
    Nov 8 at 15:13















up vote
2
down vote

favorite









up vote
2
down vote

favorite











A server "S" runs Ubuntu 18.04 LTS and Samba 4.7.6-Ubuntu. smb.conf has been left with all the default settings, except for workgroup name changed, and the following blocks added at the bottom:



[lan_share]
path = /disk2
browseable = yes
read only = yes

[lan_share_1]
path = /disk1
browseable = yes
read only = yes

[lan_share_3]
path = /disk3
browseable = yes
read only = yes


When the client was Debian 8 with packages samba and 'cifs-utils`, everything worked as expected, including ability to copy from the client-mounted share to local disks.



Now new client, workstation "W", is running Ubuntu 18.04 LTS with the latest samba and cifs-utils, and copying from shares to local is not working.



The shares on W are set up by lines in /etc/fstab as follows:



//192.168.1.233/lan_share_1 /disk1     cifs  credentials=/etc/samba/user,noexec  0 0
//192.168.1.233/lan_share /disk2 cifs credentials=/etc/samba/user,noexec 0 0
//192.168.1.233/lan_share_3 /disk3 cifs credentials=/etc/samba/user,noexec 0 0


There's a credentials file at the path listed above which, again, works fine with Debian, and probably is OK on Ubuntu too, as there are no error messages about permissions.



All this has been copied exactly from the Debian client which had no problem. Now an attempt to copy a directory tree thru the GUI file browser - say, from /disk2 to home directory - will appear to succeed at first, then the progress dialog freezes partway thru and can't even be cancelled. The progress dialog remains until the Thunar (file browser) process is killed - unless the user clicks the big red "Cancel" icon, in that case the dialog says "Cancelling..." until the process is killed. Only the first few files get copied.



I've checked that:




  • workgroup name is the same on both server and client

  • ufw on the server allows the ports in "samba" application profile

  • files in the share are OK on the server (accessible via SSH, SCP)

  • everything else works correctly on the client


I still have the Debian system where everything works normally when connecting to the same share - a whole directory structure can be copied from the share to local thru the GUI. Web searching has found various other Samba issues, some relating to going from earlier versions to Ubuntu 18, but none quite describing this situation.



Update: This ("Trouble mounting cifs shares after upgrade to 17.10") looked promising. I found out the "noexec" is unnecessary (1) and based on the former page, I replaced the ",noexec" with ",vers=2.1".



Also, on the server, did this: sudo chmod-R 775 /disk2. And with one or both of these changes in place, I can now successfully copy from the locally mounted share to home directory using command line - but it still makes Thunar hang. Now thinking it may be at least partially a GUI problem.



Update: Thanks Terrance, I'm going to check out NFS right away. I don't have Windows clients and if it's less problematic, well I just need the functionality.










share|improve this question















A server "S" runs Ubuntu 18.04 LTS and Samba 4.7.6-Ubuntu. smb.conf has been left with all the default settings, except for workgroup name changed, and the following blocks added at the bottom:



[lan_share]
path = /disk2
browseable = yes
read only = yes

[lan_share_1]
path = /disk1
browseable = yes
read only = yes

[lan_share_3]
path = /disk3
browseable = yes
read only = yes


When the client was Debian 8 with packages samba and 'cifs-utils`, everything worked as expected, including ability to copy from the client-mounted share to local disks.



Now new client, workstation "W", is running Ubuntu 18.04 LTS with the latest samba and cifs-utils, and copying from shares to local is not working.



The shares on W are set up by lines in /etc/fstab as follows:



//192.168.1.233/lan_share_1 /disk1     cifs  credentials=/etc/samba/user,noexec  0 0
//192.168.1.233/lan_share /disk2 cifs credentials=/etc/samba/user,noexec 0 0
//192.168.1.233/lan_share_3 /disk3 cifs credentials=/etc/samba/user,noexec 0 0


There's a credentials file at the path listed above which, again, works fine with Debian, and probably is OK on Ubuntu too, as there are no error messages about permissions.



All this has been copied exactly from the Debian client which had no problem. Now an attempt to copy a directory tree thru the GUI file browser - say, from /disk2 to home directory - will appear to succeed at first, then the progress dialog freezes partway thru and can't even be cancelled. The progress dialog remains until the Thunar (file browser) process is killed - unless the user clicks the big red "Cancel" icon, in that case the dialog says "Cancelling..." until the process is killed. Only the first few files get copied.



I've checked that:




  • workgroup name is the same on both server and client

  • ufw on the server allows the ports in "samba" application profile

  • files in the share are OK on the server (accessible via SSH, SCP)

  • everything else works correctly on the client


I still have the Debian system where everything works normally when connecting to the same share - a whole directory structure can be copied from the share to local thru the GUI. Web searching has found various other Samba issues, some relating to going from earlier versions to Ubuntu 18, but none quite describing this situation.



Update: This ("Trouble mounting cifs shares after upgrade to 17.10") looked promising. I found out the "noexec" is unnecessary (1) and based on the former page, I replaced the ",noexec" with ",vers=2.1".



Also, on the server, did this: sudo chmod-R 775 /disk2. And with one or both of these changes in place, I can now successfully copy from the locally mounted share to home directory using command line - but it still makes Thunar hang. Now thinking it may be at least partially a GUI problem.



Update: Thanks Terrance, I'm going to check out NFS right away. I don't have Windows clients and if it's less problematic, well I just need the functionality.







server 18.04 samba






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Nov 8 at 19:48

























asked Nov 8 at 14:05









stephen_789

1214




1214












  • +1 for a great question. Unfortunately, I have not stumbled across your issue with my network, but there were some issues I did have with cifs. Mostly cosmetics like incorrect used space reporting from server side. askubuntu.com/questions/1058815/… I ended up going with NFS on the server side but kept Samba as well. The speed on the NFS is faster and I get the correct used space reporting.
    – Terrance
    Nov 8 at 15:13




















  • +1 for a great question. Unfortunately, I have not stumbled across your issue with my network, but there were some issues I did have with cifs. Mostly cosmetics like incorrect used space reporting from server side. askubuntu.com/questions/1058815/… I ended up going with NFS on the server side but kept Samba as well. The speed on the NFS is faster and I get the correct used space reporting.
    – Terrance
    Nov 8 at 15:13


















+1 for a great question. Unfortunately, I have not stumbled across your issue with my network, but there were some issues I did have with cifs. Mostly cosmetics like incorrect used space reporting from server side. askubuntu.com/questions/1058815/… I ended up going with NFS on the server side but kept Samba as well. The speed on the NFS is faster and I get the correct used space reporting.
– Terrance
Nov 8 at 15:13






+1 for a great question. Unfortunately, I have not stumbled across your issue with my network, but there were some issues I did have with cifs. Mostly cosmetics like incorrect used space reporting from server side. askubuntu.com/questions/1058815/… I ended up going with NFS on the server side but kept Samba as well. The speed on the NFS is faster and I get the correct used space reporting.
– Terrance
Nov 8 at 15:13

















active

oldest

votes











Your Answer








StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1091132%2fcant-copy-from-samba-shares-after-upgrade-to-18-04%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown






























active

oldest

votes













active

oldest

votes









active

oldest

votes






active

oldest

votes
















draft saved

draft discarded




















































Thanks for contributing an answer to Ask Ubuntu!


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.





Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


Please pay close attention to the following guidance:


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1091132%2fcant-copy-from-samba-shares-after-upgrade-to-18-04%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

flock() on closed filehandle LOCK_FILE at /usr/bin/apt-mirror

Mangá

 ⁒  ․,‪⁊‑⁙ ⁖, ⁇‒※‌, †,⁖‗‌⁝    ‾‸⁘,‖⁔⁣,⁂‾
”‑,‥–,‬ ,⁀‹⁋‴⁑ ‒ ,‴⁋”‼ ⁨,‷⁔„ ‰′,‐‚ ‥‡‎“‷⁃⁨⁅⁣,⁔
⁇‘⁔⁡⁏⁌⁡‿‶‏⁨ ⁣⁕⁖⁨⁩⁥‽⁀  ‴‬⁜‟ ⁃‣‧⁕‮ …‍⁨‴ ⁩,⁚⁖‫ ,‵ ⁀,‮⁝‣‣ ⁑  ⁂– ․, ‾‽ ‏⁁“⁗‸ ‾… ‹‡⁌⁎‸‘ ‡⁏⁌‪ ‵⁛ ‎⁨ ―⁦⁤⁄⁕