Remote drive access bug or permission problem? (Samba/Nemo)

Questions about other topics - please check if your question fits better in another category before posting here
Forum rules
Before you post please read this

Remote drive access bug or permission problem? (Samba/Nemo)

Postby TheForumTroll on Fri Dec 14, 2012 2:11 pm

I'm not sure if this is a bug or some setting or what, but I was hoping to figure it out here, so if it is a bug it can be reported in launchpad.

First a quick explanation of the setup:
On "SERVER" (an Ubuntu headless server) i got a drive I access via Samba from my PC (Mint 14 Cinnamon, just installed, so 99,9% default settings). On the server is a lot of compressed files.

So here's the problem. There are two scenarios:
A) I mount the share myself via /etc/fstab and access it via the locally mounted folder (/disk2)
B) I access the share via NETWORK->Windows Network-> WORKGROUP -> SERVER in Nemo

Using A, I can right-click the first file in a series of compressed files and chose "Extract here" and it works fine (I.E. all the files belonging together gets decompressed). But with B, doing the exact same thing will give me an error when trying to decompress (a "Could not find the volume" error on file number two).

In other words, my mount works, Nemo's doesn't.

So is this some kind of permission problem or whatever or might it be a bug? I of course enter the same credentials in the pop-up from Nemo as I use in my credentials file for fstab, otherwise I couldn't have accessed the remote files in the first place. Not sure what options Nemo mount with though or what to look for to see what's wrong.

My fstab mount looks something like this:
Code: Select all
//SERVER_IP/SHARE_NAME  /MOUNT_POINT  cifs  rw,credentials=/home/username/.smbcredentials,uid=1000,gid=1000,file_mode=0777,dir_mode=0777,iocharset=utf8  0 0


Just to clarify. Choosing "Open with Archive Manager" instead and decompress to my home folder does not fix it. So it's not a write permission problem on the remote server.
PC: Intel I5-2500K || ASUS Sabertooth P67 || 4GB Corsair XMS3 || Gainward GTX 460 GS-GLH || OCZ Vertex 3 || Noctua NH-D14 || Corsair HX 750W || NZXT PanzerBox || Zalman ZM-MFC1+ || ASUS VW246H || Microsoft SideWinder X6 || Logitech G9 Lazer
TheForumTroll
Level 2
Level 2
 
Posts: 58
Joined: Tue Aug 21, 2012 3:47 am

Linux Mint is funded by ads and donations.
 

Re: Remote drive access bug or permission problem? (Samba/Ne

Postby altair4 on Fri Dec 14, 2012 2:46 pm

I can't reproduce this problem on my system and I'm not sure where to even start to debug it.

The Nemo mount ( which is a gvfs-mount smb://server/share ) should be mounting it with owner=group=you and with permissions of 700 - at least as far as the client is concerned. You can verify that by running the following command. Note: put quotes around the location since the gvfs mountpoint starting in Mint14 is nothing short of a mess:

Code: Select all
ls -al "/run/user/your-user-name/gvfs/smb-share:server=SERVER_IP,share=SHARE_NAME"
Please add a [SOLVED] at the end of your original subject header if your question has been answered and solved.
altair4
Level 16
Level 16
 
Posts: 6054
Joined: Tue Feb 03, 2009 10:27 am

Re: Remote drive access bug or permission problem? (Samba/Ne

Postby TheForumTroll on Fri Dec 14, 2012 3:06 pm

disregard this post. Brainfart :lol:
Last edited by TheForumTroll on Fri Dec 14, 2012 3:19 pm, edited 2 times in total.
PC: Intel I5-2500K || ASUS Sabertooth P67 || 4GB Corsair XMS3 || Gainward GTX 460 GS-GLH || OCZ Vertex 3 || Noctua NH-D14 || Corsair HX 750W || NZXT PanzerBox || Zalman ZM-MFC1+ || ASUS VW246H || Microsoft SideWinder X6 || Logitech G9 Lazer
TheForumTroll
Level 2
Level 2
 
Posts: 58
Joined: Tue Aug 21, 2012 3:47 am

Re: Remote drive access bug or permission problem? (Samba/Ne

Postby TheForumTroll on Fri Dec 14, 2012 3:15 pm

Like so?

Code: Select all
~ $ ls -al /run/user/dustie/gvfs/smb-share\:server\=server\,share\=disk2/


It shows the files on the remote share. The permissions looks fine too, I think?
Code: Select all
drwx------ 1 dustie dustie
-rwx------ 1 dustie dustie
PC: Intel I5-2500K || ASUS Sabertooth P67 || 4GB Corsair XMS3 || Gainward GTX 460 GS-GLH || OCZ Vertex 3 || Noctua NH-D14 || Corsair HX 750W || NZXT PanzerBox || Zalman ZM-MFC1+ || ASUS VW246H || Microsoft SideWinder X6 || Logitech G9 Lazer
TheForumTroll
Level 2
Level 2
 
Posts: 58
Joined: Tue Aug 21, 2012 3:47 am

Re: Remote drive access bug or permission problem? (Samba/Ne

Postby altair4 on Fri Dec 14, 2012 3:26 pm

The only thing I can think of is a problem on the server.

Can you post the output of the following from the server:
Code: Select all
testparm -s

Or if you can post the output of the entire smb.conf I can run the testparm from that.
Please add a [SOLVED] at the end of your original subject header if your question has been answered and solved.
altair4
Level 16
Level 16
 
Posts: 6054
Joined: Tue Feb 03, 2009 10:27 am

Re: Remote drive access bug or permission problem? (Samba/Ne

Postby TheForumTroll on Fri Dec 14, 2012 3:29 pm

Wait. The permissions are not the same:

Via Nemo:
Code: Select all
drwx------ 1 dustie dustie          0 Nov 10 03:14 Drivers


Via fstab:
Code: Select all
drwxr-xr-x   4 dustie dustie          0 Nov 10 03:14 Drivers



Code: Select all
~$ testparm -s
Load smb config files from /etc/samba/smb.conf
rlimit_max: increasing rlimit_max (1024) to minimum Windows limit (16384)
Processing section "[disk2]"
Processing section "[disk3]"
Loaded services file OK.
Server role: ROLE_STANDALONE
[global]
   server string = Samba Server
   log file = /var/log/samba/%m.log
   max log size = 100
   socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
   preferred master = Yes
   dns proxy = No
   idmap config * : backend = tdb

[disk2]
   comment = disk2
   path = /disk2
   valid users = dustie
   read only = No
   create mask = 0755

[disk3]
   comment = disk3
   path = /disk3
   valid users = dustie
   read only = No
   create mask = 0755
PC: Intel I5-2500K || ASUS Sabertooth P67 || 4GB Corsair XMS3 || Gainward GTX 460 GS-GLH || OCZ Vertex 3 || Noctua NH-D14 || Corsair HX 750W || NZXT PanzerBox || Zalman ZM-MFC1+ || ASUS VW246H || Microsoft SideWinder X6 || Logitech G9 Lazer
TheForumTroll
Level 2
Level 2
 
Posts: 58
Joined: Tue Aug 21, 2012 3:47 am

Re: Remote drive access bug or permission problem? (Samba/Ne

Postby altair4 on Fri Dec 14, 2012 4:01 pm

Wait. The permissions are not the same:

The resulting permissions wouldn't be the same. In fstab you specify the permissions with gvfs it's out of your control. It's sort of kind of what happens with mouning an NTFS partition. Mount it through Nemo and it's user:user 700. Mount it through fstab and it can be anything you want.

Just out of curiosity, is that the default smb.conf in an Ubuntu server? It seems to be missing some "stuff". I guess if it was a real problem it would fail with an fstab mount of it's shares. It's just that I've never seen one so sparse before.

I'm stalling for time in case you didn't pick up on it :? I'm trying to figure out why one mount method works and the other doesn't. At the moment I'm focused on that create mask value.
Please add a [SOLVED] at the end of your original subject header if your question has been answered and solved.
altair4
Level 16
Level 16
 
Posts: 6054
Joined: Tue Feb 03, 2009 10:27 am

Re: Remote drive access bug or permission problem? (Samba/Ne

Postby TheForumTroll on Fri Dec 14, 2012 4:19 pm

No, that's just what testparm prints. The smb.conf is a lot longer.


Code: Select all
# This is the main Samba configuration file. You should read the
# smb.conf(5) manual page in order to understand the options listed
# here. Samba has a huge number of configurable options (perhaps too
# many!) most of which are not shown in this example
#
# Any line which starts with a ; (semi-colon) or a # (hash)
# is a comment and is ignored. In this example we will use a #
# for commentry and a ; for parts of the config file that you
# may wish to enable
#
# NOTE: Whenever you modify this file you should run the command "testparm"
# to check that you have not made any basic syntactic errors.
#
#======================= Global Settings =====================================
[global]

# workgroup = Make sure it matches YOUR OWN NT-Domain-Name or Workgroup-Name
   workgroup = workgroup

# server string is the equivalent of the NT Description field
   server string = Samba Server

# This option is important for security. It allows you to restrict
# connections to machines which are on your local network. The
# following example restricts access to two C class networks and
# the "loopback" interface. For more examples of the syntax see
# the smb.conf man page
;   hosts allow = 192.168.1. 192.168.2. 127.

# if you want to automatically load your printer list rather
# than setting them up individually then you'll need this
#   printcap name = /etc/printcap
#   load printers = yes

# It should not be necessary to spell out the print system type unless
# yours is non-standard. Currently supported print systems include:
# bsd, sysv, plp, lprng, aix, hpux, qnx
;   printing = bsd

# Uncomment this if you want a guest account, you must add this to /etc/passwd
# otherwise the user "nobody" is used
;  guest account = pcguest

# this tells Samba to use a separate log file for each machine
# that connects
   log file = /var/log/samba/%m.log
# all log information in one file
#   log file = /var/log/samba/smbd.log

# Put a capping on the size of the log files (in Kb).
   max log size = 100

# Security mode. Most people will want user level security. See
# security_level.txt for details.
# Use password server option only with security = server
;   password server = <NT-Server-Name>
security = user
# Password Level allows matching of _n_ characters of the password for
# all combinations of upper and lower case.
;  password level = 8
;  username level = 8

# You may wish to use password encryption. Please read
# ENCRYPTION.txt, Win95.txt and WinNT.txt in the Samba documentation.
# Do not enable this option unless you have read those documents
;  encrypt passwords = yes
;  smb passwd file = /etc/samba/smbpasswd

# The following are needed to allow password changing from Windows to
# update the Linux system password also.
# NOTE: Use these with 'encrypt passwords' and 'smb passwd file' above.
# NOTE2: You do NOT need these to allow workstations to change only
#        the encrypted SMB passwords. They allow the Unix password
#        to be kept in sync with the SMB password.
;  unix password sync = Yes
;  passwd program = /usr/bin/passwd %u
;  passwd chat = *New*UNIX*password* %n\n *ReType*new*UNIX*password* %n\n *passwd:*all*authentication*tokens*updated*successfully*

# Unix users can map to different SMB User names
;  username map = /etc/samba/smbusers

# Using the following line enables you to customise your configuration
# on a per machine basis. The %m gets replaced with the netbios name
# of the machine that is connecting
;   include = /etc/samba/smb.conf.%m

# Most people will find that this option gives better performance.
# See speed.txt and the manual pages for details
   socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192

# Configure Samba to use multiple interfaces
# If you have multiple network interfaces then you must list them
# here. See the man page for details.
;   interfaces = 192.168.12.2/24 192.168.13.2/24

# Configure remote browse list synchronisation here
#  request announcement to, or browse list sync from:
#   a specific host or from / to a whole subnet (see below)
;   remote browse sync = 192.168.3.25 192.168.5.255
# Cause this host to announce itself to local subnets here
;   remote announce = 192.168.1.255 192.168.2.44

# Browser Control Options:
# set local master to no if you don't want Samba to become a master
# browser on your network. Otherwise the normal election rules apply
;   local master = no

# OS Level determines the precedence of this server in master browser
# elections. The default value should be reasonable
;   os level = 33

# Domain Master specifies Samba to be the Domain Master Browser. This
# allows Samba to collate browse lists between subnets. Don't use this
# if you already have a Windows NT domain controller doing this job
;   domain master = yes

# Preferred Master causes Samba to force a local browser election on startup
# and gives it a slightly higher chance of winning the election
   preferred master = yes

# Enable this if you want Samba to be a domain logon server for
# Windows95 workstations.
;   domain logons = yes

# if you enable domain logons then you may want a per-machine or
# per user logon script
# run a specific logon batch file per workstation (machine)
;   logon script = %m.bat
# run a specific logon batch file per username
;   logon script = %U.bat

# Where to store roving profiles (only for Win95 and WinNT)
#        %L substitutes for this servers netbios name, %U is username
#        You must uncomment the [Profiles] share below
;   logon path = \\%L\Profiles\%U

# All NetBIOS names must be resolved to IP Addresses
# 'Name Resolve Order' allows the named resolution mechanism to be specified
# the default order is "host lmhosts wins bcast". "host" means use the unix
# system gethostbyname() function call that will use either /etc/hosts OR
# DNS or NIS depending on the settings of /etc/host.config, /etc/nsswitch.conf
# and the /etc/resolv.conf file. "host" therefore is system configuration
# dependant. This parameter is most often of use to prevent DNS lookups
# in order to resolve NetBIOS names to IP Addresses. Use with care!
# The example below excludes use of name resolution for machines that are NOT
# on the local network segment
# - OR - are not deliberately to be known via lmhosts or via WINS.
; name resolve order = wins lmhosts bcast

# Windows Internet Name Serving Support Section:
# WINS Support - Tells the NMBD component of Samba to enable it's WINS Server
;   wins support = yes

# WINS Server - Tells the NMBD components of Samba to be a WINS Client
#   Note: Samba can be either a WINS Server, or a WINS Client, but NOT both
;   wins server = w.x.y.z

# WINS Proxy - Tells Samba to answer name resolution queries on
# behalf of a non WINS capable client, for this to work there must be
# at least one   WINS Server on the network. The default is NO.
;   wins proxy = yes

# DNS Proxy - tells Samba whether or not to try to resolve NetBIOS names
# via DNS nslookups. The built-in default for versions 1.9.17 is yes,
# this has been changed in version 1.9.18 to no.
   dns proxy = no

# Case Preservation can be handy - system default is _no_
# NOTE: These can be set on a per share basis
;  preserve case = no
;  short preserve case = no
# Default case is normally upper case for all DOS files
;  default case = lower
# Be very careful with case sensitivity - it can break things!
;  case sensitive = no

#============================ Share Definitions ==============================
#   idmap uid = 16777216-33554431
#   idmap gid = 16777216-33554431
#   template shell = /bin/false
#   username map = /etc/samba/smbusers
#   winbind use default domain = no
#[homes]
#   comment = Home Directories
#   browseable = no
#   writeable = yes

# Un-comment the following and create the netlogon directory for Domain Logons
; [netlogon]
;   comment = Network Logon Service
;   path = /home/netlogon
;   guest ok = yes
;   writable = no
;   share modes = no


# Un-comment the following to provide a specific roving profile share
# the default is to use the user's home directory
;[Profiles]
;    path = /home/profiles
;    browseable = no
;    guest ok = yes


# NOTE: If you have a BSD-style print system there is no need to
# specifically define each individual printer
#[printers]
#   comment = All Printers
#   path = /var/spool/samba
#   browseable = no
# Set public = yes to allow user 'guest account' to print
#   printable = yes

# This one is useful for people to share files
;[tmp]
;   comment = Temporary file space
;   path = /tmp
;   read only = no
;   public = yes

# A publicly accessible directory, but read only, except for people in
# the "staff" group
;[public]
;   comment = Public Stuff
;   path = /home/samba
;   public = yes
;   read only = yes
;   write list = @staff

# Other examples.
#
# A private printer, usable only by fred. Spool data will be placed in fred's
# home directory. Note that fred must have write access to the spool directory,
# wherever it is.
;[fredsprn]
;   comment = Fred's Printer
;   valid users = fred
;   path = /homes/fred
;   printer = freds_printer
;   public = no
;   writable = no
;   printable = yes

# A private directory, usable only by fred. Note that fred requires write
# access to the directory.
;[fredsdir]
;   comment = Fred's Service
;   path = /usr/somewhere/private
;   valid users = fred
;   public = no
;   writable = yes
;   printable = no

# a service which has a different directory for each machine that connects
# this allows you to tailor configurations to incoming machines. You could
# also use the %u option to tailor it by user name.
# The %m gets replaced with the machine name that is connecting.
;[pchome]
;  comment = PC Directories
;  path = /usr/pc/%m
;  public = no
;  writable = yes

# A publicly accessible directory, read/write to all users. Note that all files
# created in the directory by users will be owned by the default user, so
# any user with access can delete any other user's files. Obviously this
# directory must be writable by the default user. Another user could of course
# be specified, in which case all files would be owned by that user instead.
;[public]
;   path = /usr/somewhere/else/public
;   public = yes
;   only guest = yes
;   writable = yes
;   printable = no

# The following two entries demonstrate how to share a directory so that two
# users can place files there that will be owned by the specific users. In this
# setup, the directory should be writable by both users and should have the
# sticky bit set on it to prevent abuse. Obviously this could be extended to
# as many users as required.
[disk2]
   comment = disk2
   path = /disk2
   valid users = dustie
   public = no
   writable = yes
   printable = no
   create mask = 0755

[disk3]
   comment = disk3
   path = /disk3
   valid users = dustie
   public = no
   writable = yes
   printable = no
   create mask = 0755
 


I just changed the create mask to 755 as that was default AFAIK. It was 765 before (including when I posted here).

EDIT: I actually created a topic in another forum about what permissions would be the best in this case, since I'm sure they are far from optimal.
PC: Intel I5-2500K || ASUS Sabertooth P67 || 4GB Corsair XMS3 || Gainward GTX 460 GS-GLH || OCZ Vertex 3 || Noctua NH-D14 || Corsair HX 750W || NZXT PanzerBox || Zalman ZM-MFC1+ || ASUS VW246H || Microsoft SideWinder X6 || Logitech G9 Lazer
TheForumTroll
Level 2
Level 2
 
Posts: 58
Joined: Tue Aug 21, 2012 3:47 am

Re: Remote drive access bug or permission problem? (Samba/Ne

Postby altair4 on Fri Dec 14, 2012 4:35 pm

Smb.conf contains only additions or overrides to the default Samba setup. Testparm shows the affects of smb.conf on those defaults. It resembles a debian default smb.conf more than anything else. For example you have "map to guest = Bad User" missing. That means the default is in place which is "map to guest = Never". Not an issue with your setup it just things like that and some pam related things seem to have disappeared.

Anyway I'm no closer at the moment to figuring out what the issue is here and why it's not an issue with my setup.
Please add a [SOLVED] at the end of your original subject header if your question has been answered and solved.
altair4
Level 16
Level 16
 
Posts: 6054
Joined: Tue Feb 03, 2009 10:27 am

Re: Remote drive access bug or permission problem? (Samba/Ne

Postby TheForumTroll on Fri Dec 14, 2012 4:42 pm

I see. I must say that I have no idea what has been changed in the smb.conf as the server is old and Ubuntu has been upgraded a few times.

Thanks for trying though :D
PC: Intel I5-2500K || ASUS Sabertooth P67 || 4GB Corsair XMS3 || Gainward GTX 460 GS-GLH || OCZ Vertex 3 || Noctua NH-D14 || Corsair HX 750W || NZXT PanzerBox || Zalman ZM-MFC1+ || ASUS VW246H || Microsoft SideWinder X6 || Logitech G9 Lazer
TheForumTroll
Level 2
Level 2
 
Posts: 58
Joined: Tue Aug 21, 2012 3:47 am

Re: Remote drive access bug or permission problem? (Samba/Ne

Postby TheForumTroll on Sat Dec 15, 2012 12:40 pm

Okay, this is getting stranger by the minute, me thinks..

Looking at a file going through my mount gives follow up archives (.01 for example) this icon: Image

But going through Nemo's mount gives me this icon on the same file: Image

What the... :roll:

I tried tar'ing a file and moving it to the share. Both mounts work fine as long as there is only one file to decompress.
PC: Intel I5-2500K || ASUS Sabertooth P67 || 4GB Corsair XMS3 || Gainward GTX 460 GS-GLH || OCZ Vertex 3 || Noctua NH-D14 || Corsair HX 750W || NZXT PanzerBox || Zalman ZM-MFC1+ || ASUS VW246H || Microsoft SideWinder X6 || Logitech G9 Lazer
TheForumTroll
Level 2
Level 2
 
Posts: 58
Joined: Tue Aug 21, 2012 3:47 am

Linux Mint is funded by ads and donations.
 

Return to Other topics

Who is online

Users browsing this forum: No registered users and 2 guests