Samba mount issue under Ubuntu 17.10
Clash Royale CLAN TAG#URR8PPP
up vote
0
down vote
favorite
I have Ubuntu 16.04 running a samba server and another 16.04 box that mounts it without issue using the fstab line //192.168.0.102/share /mnt/raid cifs user=myuser,pass=mypass
. When I mount the share, the files all show the proper user/group and when coping files to the share, the mode (ie 0444) is preserved.
With another machine running Ubuntu 17.10, the same fstab line causes the mount to list everything on the share as user/group root:root instead of myuser:myuser. I can force the user/group to be correct by adding uid=1000,gid=1000
to the fstab line but when copying files to the share, the permissions are no longer preserved (they all show up as 0755).
Any ideas on what has changed that might be causing this issue and how I can fix it would be appreciated. This samba share has worked correctly for me across multiple versions of Linux so I'm fairly certain the issue is on the new Ubuntu 17.10 side but I not certain if it's a change in the security policies or something in the cifs library itself.
ubuntu networking samba
add a comment |Â
up vote
0
down vote
favorite
I have Ubuntu 16.04 running a samba server and another 16.04 box that mounts it without issue using the fstab line //192.168.0.102/share /mnt/raid cifs user=myuser,pass=mypass
. When I mount the share, the files all show the proper user/group and when coping files to the share, the mode (ie 0444) is preserved.
With another machine running Ubuntu 17.10, the same fstab line causes the mount to list everything on the share as user/group root:root instead of myuser:myuser. I can force the user/group to be correct by adding uid=1000,gid=1000
to the fstab line but when copying files to the share, the permissions are no longer preserved (they all show up as 0755).
Any ideas on what has changed that might be causing this issue and how I can fix it would be appreciated. This samba share has worked correctly for me across multiple versions of Linux so I'm fairly certain the issue is on the new Ubuntu 17.10 side but I not certain if it's a change in the security policies or something in the cifs library itself.
ubuntu networking samba
add a comment |Â
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I have Ubuntu 16.04 running a samba server and another 16.04 box that mounts it without issue using the fstab line //192.168.0.102/share /mnt/raid cifs user=myuser,pass=mypass
. When I mount the share, the files all show the proper user/group and when coping files to the share, the mode (ie 0444) is preserved.
With another machine running Ubuntu 17.10, the same fstab line causes the mount to list everything on the share as user/group root:root instead of myuser:myuser. I can force the user/group to be correct by adding uid=1000,gid=1000
to the fstab line but when copying files to the share, the permissions are no longer preserved (they all show up as 0755).
Any ideas on what has changed that might be causing this issue and how I can fix it would be appreciated. This samba share has worked correctly for me across multiple versions of Linux so I'm fairly certain the issue is on the new Ubuntu 17.10 side but I not certain if it's a change in the security policies or something in the cifs library itself.
ubuntu networking samba
I have Ubuntu 16.04 running a samba server and another 16.04 box that mounts it without issue using the fstab line //192.168.0.102/share /mnt/raid cifs user=myuser,pass=mypass
. When I mount the share, the files all show the proper user/group and when coping files to the share, the mode (ie 0444) is preserved.
With another machine running Ubuntu 17.10, the same fstab line causes the mount to list everything on the share as user/group root:root instead of myuser:myuser. I can force the user/group to be correct by adding uid=1000,gid=1000
to the fstab line but when copying files to the share, the permissions are no longer preserved (they all show up as 0755).
Any ideas on what has changed that might be causing this issue and how I can fix it would be appreciated. This samba share has worked correctly for me across multiple versions of Linux so I'm fairly certain the issue is on the new Ubuntu 17.10 side but I not certain if it's a change in the security policies or something in the cifs library itself.
ubuntu networking samba
asked Oct 20 '17 at 16:10
bivouac0
1514
1514
add a comment |Â
add a comment |Â
2 Answers
2
active
oldest
votes
up vote
5
down vote
accepted
They've changed the default dialect to SMB3 in mount.cifs. Originally it defaulted to SMB1. To get get the same behavior as Ubuntu 16.04 you add vers=1.0
to the mount options. With this option present, I now get the correct user/group and permissions are preserved when copying.
add a comment |Â
up vote
0
down vote
Try the following, direct in the console. Works fine for me.
sudo mount -t cifs -o vers=1.0,username=myuser,pass=mypass //192.168.0.102/share /mnt/raid
add a comment |Â
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
5
down vote
accepted
They've changed the default dialect to SMB3 in mount.cifs. Originally it defaulted to SMB1. To get get the same behavior as Ubuntu 16.04 you add vers=1.0
to the mount options. With this option present, I now get the correct user/group and permissions are preserved when copying.
add a comment |Â
up vote
5
down vote
accepted
They've changed the default dialect to SMB3 in mount.cifs. Originally it defaulted to SMB1. To get get the same behavior as Ubuntu 16.04 you add vers=1.0
to the mount options. With this option present, I now get the correct user/group and permissions are preserved when copying.
add a comment |Â
up vote
5
down vote
accepted
up vote
5
down vote
accepted
They've changed the default dialect to SMB3 in mount.cifs. Originally it defaulted to SMB1. To get get the same behavior as Ubuntu 16.04 you add vers=1.0
to the mount options. With this option present, I now get the correct user/group and permissions are preserved when copying.
They've changed the default dialect to SMB3 in mount.cifs. Originally it defaulted to SMB1. To get get the same behavior as Ubuntu 16.04 you add vers=1.0
to the mount options. With this option present, I now get the correct user/group and permissions are preserved when copying.
answered Oct 20 '17 at 23:00
bivouac0
1514
1514
add a comment |Â
add a comment |Â
up vote
0
down vote
Try the following, direct in the console. Works fine for me.
sudo mount -t cifs -o vers=1.0,username=myuser,pass=mypass //192.168.0.102/share /mnt/raid
add a comment |Â
up vote
0
down vote
Try the following, direct in the console. Works fine for me.
sudo mount -t cifs -o vers=1.0,username=myuser,pass=mypass //192.168.0.102/share /mnt/raid
add a comment |Â
up vote
0
down vote
up vote
0
down vote
Try the following, direct in the console. Works fine for me.
sudo mount -t cifs -o vers=1.0,username=myuser,pass=mypass //192.168.0.102/share /mnt/raid
Try the following, direct in the console. Works fine for me.
sudo mount -t cifs -o vers=1.0,username=myuser,pass=mypass //192.168.0.102/share /mnt/raid
answered Oct 29 '17 at 22:11
matson kepson
1
1
add a comment |Â
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f399378%2fsamba-mount-issue-under-ubuntu-17-10%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password