[SOLVED] Slow write speeds to Synology NAS shares using pam_mount.

Questions about Wi-Fi and other network devices, file sharing, firewalls, connection sharing etc
Forum rules
Before you post read how to get help. Topics in this forum are automatically closed 6 months after creation.
Locked
ehoitinga

[SOLVED] Slow write speeds to Synology NAS shares using pam_mount.

Post by ehoitinga »

Hello,

I have a strange problem concerning write speeds when copying a file with Nemo (the default file manager in Linux Mint) from my Linux Mint 19.0 laptop to my Synology NAS server. Copying is done by cabled network. Wireless adaptor is switched off. To test this I took a large video file with a size of 14GB. The shares on my NAS are mounted on login as CIFS to my laptop using pam_mount. The read speeds are around 82MBytes/s and seem fairly normal for a 1GB cable connected network. Although when I start the copy it takes about 6 or 7 seconds before the copy actually starts. The write speeds however are horrible. The are about 1/10 of what about I expect, around 9MBytes/s. I have this problem since a fresh install of Mint 19.0.

On the same laptop I run Windows 10 in a virtual machine (VirtualBox) with bridged adaptor. The read and write speeds in Windows are what I expect. Read: 81MBytes/s and Write: 96,6Mbytes/s. So I can rule out my NAS, my Switch and my cabling (CAT6A) to be the problem.

Also when I open a file with LibreOffice 6.0 (Calc or Draw or other, it does not matter) it takes LibreOffice a long time (about 10 seconds) to open the file. The file itself is 22KB, so this is ridiculous. During these 10 seconds the whole system stays frozen. Once LibreOffice is open, it opens a second file as fast as it should. I don't know if this problem is related but it's driving me mad.

My NAS server supports SMBv1 to SMBv3. Yes also SMBv1 because my Sonos equipment does not support SMB protocol higher then v1. :x Also my NAS acts as a WINS server. The option "wins support=yes" in the smb.conf file on my NAS is set.

Anyone experiencing this weird behaviour?

Thanks in advance.

The smb.conf file on my laptop is like this:

Code: Select all

#
# Sample configuration file for the Samba suite for Debian GNU/Linux.
#
#
# 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 most of which 
# are not shown in this example
#
# Some options that are often worth tuning have been included as
# commented-out examples in this file.
#  - When such options are commented with ";", the proposed setting
#    differs from the default Samba behaviour
#  - When commented with "#", the proposed setting is the default
#    behaviour of Samba but the option is considered important
#    enough to be mentioned here
#
# 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]

## Browsing/Identification ###

# Change this to the workgroup/NT-domain name your Samba server will part of
  workgroup = HOME
  # client min protocol = NT1
  client min protocol = SMB2
  client max protocol = SMB3

# server string is the equivalent of the NT Description field
  server string = %h server (Samba, Ubuntu)

# Windows Internet Name Serving Support Section:
# WINS Support - Tells the NMBD component of Samba to enable its WINS Server
#  wins support = no

# 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 = 192.168.1.248

# This will prevent nmbd to search for NetBIOS names through DNS.
  dns proxy = no

#### Networking ####

# The specific set of interfaces / networks to bind to
# This can be either the interface name or an IP address/netmask;
# interface names are normally preferred
;   interfaces = 127.0.0.0/8 eth0

# Only bind to the named interfaces and/or networks; you must use the
# 'interfaces' option above to use this.
# It is recommended that you enable this feature if your Samba machine is
# not protected by a firewall or is a firewall itself.  However, this
# option cannot handle dynamic or non-broadcast interfaces correctly.
;   bind interfaces only = yes



#### Debugging/Accounting ####

# This tells Samba to use a separate log file for each machine
# that connects
   log file = /var/log/samba/log.%m

# Cap the size of the individual log files (in KiB).
   max log size = 1000

# If you want Samba to only log through syslog then set the following
# parameter to 'yes'.
#   syslog only = no

# We want Samba to log a minimum amount of information to syslog. Everything
# should go to /var/log/samba/log.{smbd,nmbd} instead. If you want to log
# through syslog you should set the following parameter to something higher.
   syslog = 0

# Do something sensible when Samba crashes: mail the admin a backtrace
   panic action = /usr/share/samba/panic-action %d


####### Authentication #######

# Server role. Defines in which mode Samba will operate. Possible
# values are "standalone server", "member server", "classic primary
# domain controller", "classic backup domain controller", "active
# directory domain controller". 
#
# Most people will want "standalone sever" or "member server".
# Running as "active directory domain controller" will require first
# running "samba-tool domain provision" to wipe databases and create a
# new domain.
  server role = standalone server

# If you are using encrypted passwords, Samba will need to know what
# password database type you are using.  
  passdb backend = tdbsam

  obey pam restrictions = yes

# This boolean parameter controls whether Samba attempts to sync the Unix
# password with the SMB password when the encrypted SMB password in the
# passdb is changed.
  unix password sync = yes

# For Unix password sync to work on a Debian GNU/Linux system, the following
# parameters must be set (thanks to Ian Kahan <<kahan@informatik.tu-muenchen.de> for
# sending the correct chat script for the passwd program in Debian Sarge).
  passwd program = /usr/bin/passwd %u
  passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* .

# This boolean controls whether PAM will be used for password changes
# when requested by an SMB client instead of the program listed in
# 'passwd program'. The default is 'no'.
  pam password change = yes

# This option controls how unsuccessful authentication attempts are mapped
# to anonymous connections
  map to guest = bad user

########## Domains ###########

#
# The following settings only takes effect if 'server role = primary
# classic domain controller', 'server role = backup domain controller'
# or 'domain logons' is set 
#

# It specifies the location of the user's
# profile directory from the client point of view) The following
# required a [profiles] share to be setup on the samba server (see
# below)
;   logon path = \\%N\profiles\%U
# Another common choice is storing the profile in the user's home directory
# (this is Samba's default)
#   logon path = \\%N\%U\profile

# The following setting only takes effect if 'domain logons' is set
# It specifies the location of a user's home directory (from the client
# point of view)
;   logon drive = H:
#   logon home = \\%N\%U

# The following setting only takes effect if 'domain logons' is set
# It specifies the script to run during logon. The script must be stored
# in the [netlogon] share
# NOTE: Must be store in 'DOS' file format convention
;   logon script = logon.cmd

# This allows Unix users to be created on the domain controller via the SAMR
# RPC pipe.  The example command creates a user account with a disabled Unix
# password; please adapt to your needs
; add user script = /usr/sbin/adduser --quiet --disabled-password --gecos "" %u

# This allows machine accounts to be created on the domain controller via the 
# SAMR RPC pipe.  
# The following assumes a "machines" group exists on the system
; add machine script  = /usr/sbin/useradd -g machines -c "%u machine account" -d /var/lib/samba -s /bin/false %u

# This allows Unix groups to be created on the domain controller via the SAMR
# RPC pipe.  
; add group script = /usr/sbin/addgroup --force-badname %g

############ Misc ############

# 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 = /home/samba/etc/smb.conf.%m

# Some defaults for winbind (make sure you're not using the ranges
# for something else.)
;   idmap uid = 10000-20000
;   idmap gid = 10000-20000
;   template shell = /bin/bash

# Setup usershare options to enable non-root users to share folders
# with the net usershare command.

# Maximum number of usershare. 0 (default) means that usershare is disabled.
;   usershare max shares = 100

# Allow users who've been granted usershare privileges to create
# public shares, not just authenticated ones
   usershare allow guests = yes

#======================= Share Definitions =======================

# Un-comment the following (and tweak the other settings below to suit)
# to enable the default home directory shares. This will share each
# user's home directory as \\server\username
;[homes]
;   comment = Home Directories
;   browseable = no

# By default, the home directories are exported read-only. Change the
# next parameter to 'no' if you want to be able to write to them.
;   read only = yes

# File creation mask is set to 0700 for security reasons. If you want to
# create files with group=rw permissions, set next parameter to 0775.
;   create mask = 0700

# Directory creation mask is set to 0700 for security reasons. If you want to
# create dirs. with group=rw permissions, set next parameter to 0775.
;   directory mask = 0700

# By default, \\server\username shares can be connected to by anyone
# with access to the samba server.
# Un-comment the following parameter to make sure that only "username"
# can connect to \\server\username
# This might need tweaking when using external authentication schemes
;   valid users = %S

# Un-comment the following and create the netlogon directory for Domain Logons
# (you need to configure Samba to act as a domain controller too.)
;[netlogon]
;   comment = Network Logon Service
;   path = /home/samba/netlogon
;   guest ok = yes
;   read only = yes

# Un-comment the following and create the profiles directory to store
# users profiles (see the "logon path" option above)
# (you need to configure Samba to act as a domain controller too.)
# The path below should be writable by all users so that their
# profile directory may be created the first time they log on
;[profiles]
;   comment = Users profiles
;   path = /home/samba/profiles
;   guest ok = no
;   browseable = no
;   create mask = 0600
;   directory mask = 0700

[printers]
   comment = All Printers
   browseable = no
   path = /var/spool/samba
   printable = yes
   guest ok = no
   read only = yes
   create mask = 0700

# Windows clients look for this share name as a source of downloadable
# printer drivers
[print$]
   comment = Printer Drivers
   path = /var/lib/samba/printers
   browseable = yes
   read only = yes
   guest ok = no
# Uncomment to allow remote administration of Windows print drivers.
# You may need to replace 'lpadmin' with the name of the group your
# admin users are members of.
# Please note that you also need to set appropriate Unix permissions
# to the drivers directory for these users to have write rights in it
;   write list = root, @lpadmin
The smb.conf file on my NAS is like this:

Code: Select all

[global]
    printcap name=cups
    winbind enum groups=yes
    include=/var/tmp/nginx/smb.netbios.aliases.conf
    encrypt passwords=yes
    min protocol=NT1
    security=user
    local master=yes
    realm=*
    name resolve order=wins hosts lmhosts bcast
    syno sync dctime=no
    passdb backend=smbpasswd
    printing=cups
    max protocol=SMB3
    winbind enum users=yes
    wins support=yes
    load printers=yes
    workgroup=HOME
The /etc/security/pam_mount.conf.xml file on my laptop is like this:

Code: Select all

<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE pam_mount SYSTEM "pam_mount.conf.xml.dtd">
<pam_mount>
  <!-- Disable debugging 
  -->
  <debug
  		enable="0" 
  />

  <!-- All options listed in allow *may* appear in the option list of per-user volume mounts.
       These options do not apply to the master file.
  -->
  <mntoptions 
  		allow="nosuid,nodev,workgroup,nosetuids,noexec,nosuid,dir_mode,file_mode,uid,gid" 
  />

  <!-- All options listed in require must appear in the option list of per-user volume mounts.
       These options also apply to the master file.
  -->
  <mntoptions
  		require="nosuid,nodev,nofail" 
  />

  <!-- Programs exist that do not terminate when the session is closed. pam_mount can be configured 
       to kill these processes and optionally wait before sending signals. -->
  <logout 
  		wait="0" hup="0" term="yes" kill="0" 
  />

  <!-- Controls automatic creation and removal of mountpoints.
  -->
  <mkmountpoint enable="1" remove="true" />

  <!-- Map some shares residing on the NAS-SERVER to the users home directory
  -->
  <volume
		options="workgroup=HOME,nosuid,nodev,nofail,vers=3.0,uid=%(USERUID),gid=%(USERGID),dir_mode=0750,file_mode=0640"
		user="*"
		fstype="cifs"
		server="192.168.1.248"
		path="backup"
		mountpoint="/home/%(USER)/Backup"
  />
  <volume
		options="workgroup=HOME,nosuid,nodev,nofail,vers=3.0,uid=%(USERUID),gid=%(USERGID),dir_mode=0750,file_mode=0640"
		user="*"
		fstype="cifs"
		server="192.168.1.248"
		path="documents"
		mountpoint="/home/%(USER)/Documents"
  />
  <volume
		options="workgroup=HOME,nosuid,nodev,nofail,vers=3.0,uid=%(USERUID),gid=%(USERGID),dir_mode=0750,file_mode=0640"
		user="*"
		fstype="cifs"
		server="192.168.1.248"
		path="download"
		mountpoint="/home/%(USER)/Downloads"
  />
  <volume
		options="workgroup=HOME,nosuid,nodev,nofail,vers=3.0,uid=%(USERUID),gid=%(USERGID),dir_mode=0750,file_mode=0640"
		user="*"
		fstype="cifs"
		server="192.168.1.248"
		path="fax"
		mountpoint="/home/%(USER)/Fax"
  />
  <volume
		options="workgroup=HOME,nosuid,nodev,nofail,vers=3.0,uid=%(USERUID),gid=%(USERGID),dir_mode=0750,file_mode=0640"
		user="*"
		fstype="cifs"
		server="192.168.1.248"
		path="music"
		mountpoint="/home/%(USER)/Music"
  />
  <volume
		options="workgroup=HOME,nosuid,nodev,nofail,vers=3.0,uid=%(USERUID),gid=%(USERGID),dir_mode=0750,file_mode=0640"
		user="*"
		fstype="cifs"
		server="192.168.1.248"
		path="photo"
		mountpoint="/home/%(USER)/Pictures"
  />
  <volume
		options="workgroup=HOME,nosuid,nodev,nofail,vers=3.0,uid=%(USERUID),gid=%(USERGID),dir_mode=0750,file_mode=0640"
		user="*"
		fstype="cifs"
		server="192.168.1.248"
		path="scans"
		mountpoint="/home/%(USER)/Scans"
  />
  <volume
		options="workgroup=HOME,nosuid,nodev,nofail,vers=3.0,uid=%(USERUID),gid=%(USERGID),dir_mode=0750,file_mode=0640"
		user="*"
		fstype="cifs"
		server="192.168.1.248"
		path="video"
		mountpoint="/home/%(USER)/Videos"
  />
  <volume
		options="workgroup=HOME,nosuid,nodev,nofail,vers=3.0,uid=%(USERUID),gid=%(USERGID),dir_mode=0750,file_mode=0640"
		user="*"
		fstype="cifs"
		server="192.168.1.248"
		path="web"
		mountpoint="/home/%(USER)/Websites"
  />
</pam_mount>
Last edited by LockBot on Wed Dec 28, 2022 7:16 am, edited 6 times in total.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
ehoitinga

Re: Slow write speeds to my Synology NAS server.

Post by ehoitinga »

Hi there,

I did some testing this morning. I suspected pam_mount was causing the problem.

When I connect to a NAS share just by typing smb://nas-server/video/ in Nemo the read speed is around 72MBytes/s and it starts copying right away, no delay this time. The write speed is around 58MBytes/s. Not the optimal I can reach but a lot, lot better.

Also the LibreOffice problem is gone. It opens a file right away now.

So pam_mount seems to be the problem. So there must be either a configuration error in the pam_mount configuration file or Nemo and pam_mount don't like each other.

Will investigate further. In the meantime, if anyone has a suggestion please step forward :D

Thanks
ehoitinga

Re: Slow write speeds to Synology NAS shares using pam_mount.

Post by ehoitinga »

Hi there,

Further investigation on the problem reveals some errors in auth.log:

Code: Select all

Aug  9 12:34:59 laptop-erik lightdm: pam_unix(lightdm-greeter:session): session closed for user lightdm
Aug  9 12:34:59 laptop-erik lightdm: (mount.c:72): umount messages:
Aug  9 12:34:59 laptop-erik lightdm: (mount.c:76): umount: /home/lightdm/Websites: no mount point specified.
Aug  9 12:34:59 laptop-erik lightdm: (mount.c:892): unmount of web failed
Aug  9 12:34:59 laptop-erik lightdm: (mount.c:72): umount messages:
Aug  9 12:34:59 laptop-erik lightdm: (mount.c:76): umount: /home/lightdm/Videos: no mount point specified.
Aug  9 12:34:59 laptop-erik lightdm: (mount.c:892): unmount of video failed
Aug  9 12:34:59 laptop-erik lightdm: (mount.c:72): umount messages:
Aug  9 12:34:59 laptop-erik lightdm: (mount.c:76): umount: /home/lightdm/Scans: no mount point specified.
Aug  9 12:34:59 laptop-erik lightdm: (mount.c:892): unmount of scans failed
Aug  9 12:34:59 laptop-erik lightdm: (mount.c:72): umount messages:
Aug  9 12:34:59 laptop-erik lightdm: (mount.c:76): umount: /home/lightdm/Pictures: no mount point specified.
Aug  9 12:34:59 laptop-erik lightdm: (mount.c:892): unmount of photo failed
Aug  9 12:34:59 laptop-erik lightdm: (mount.c:72): umount messages:
Aug  9 12:34:59 laptop-erik lightdm: (mount.c:76): umount: /home/lightdm/Music: no mount point specified.
Aug  9 12:34:59 laptop-erik lightdm: (mount.c:892): unmount of music failed
Aug  9 12:34:59 laptop-erik lightdm: (mount.c:72): umount messages:
Aug  9 12:34:59 laptop-erik lightdm: (mount.c:76): umount: /home/lightdm/Fax: no mount point specified.
Aug  9 12:34:59 laptop-erik lightdm: (mount.c:892): unmount of fax failed
Aug  9 12:34:59 laptop-erik lightdm: (mount.c:72): umount messages:
Aug  9 12:34:59 laptop-erik lightdm: (mount.c:76): umount: /home/lightdm/Downloads: no mount point specified.
Aug  9 12:34:59 laptop-erik lightdm: (mount.c:892): unmount of download failed
Aug  9 12:34:59 laptop-erik lightdm: (mount.c:72): umount messages:
Aug  9 12:34:59 laptop-erik lightdm: (mount.c:76): umount: /home/lightdm/Documents: no mount point specified.
Aug  9 12:34:59 laptop-erik lightdm: (mount.c:892): unmount of documents failed
Aug  9 12:34:59 laptop-erik lightdm: (mount.c:72): umount messages:
Aug  9 12:34:59 laptop-erik lightdm: (mount.c:76): umount: /home/lightdm/Backup: no mount point specified.
Aug  9 12:34:59 laptop-erik lightdm: (mount.c:892): unmount of backup failed
Aug  9 12:34:59 laptop-erik systemd-logind[867]: Removed session c1.
Aug  9 12:34:59 laptop-erik lightdm: pam_unix(lightdm:session): session opened for user erik by (uid=0)
Aug  9 12:34:59 laptop-erik systemd: pam_unix(systemd-user:session): session closed for user lightdm
Aug  9 12:34:59 laptop-erik systemd-logind[867]: New session c2 of user erik.
Aug  9 12:34:59 laptop-erik systemd: pam_unix(systemd-user:session): session opened for user erik by (uid=0)
When I log in the variable %(USER) in pam_mount.conf.xml is translated to my username. However when I log out the variable %(USER) is translated to "lightdm" and the unmount fails as shown above in the log file. When I specify my username hardcoded in the file pam_mount.conf.xml the above error messages ar gone.

However on re-inspection of the auth.log file I get "mount error(13): Permission denied" but the shares are properly mounted. Maybe I should put the option "<luserconf name=".pam_mount.conf.xml" />" in the master file and create a .pam_mount.conf.xml in my home directory and specify the volumes there.
Will test this, will let you know.

Code: Select all

Aug  9 12:51:08 laptop-erik polkitd(authority=local): Unregistered Authentication Agent for unix-session:c4 (system bus name :1.93, object path /org/gnome/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) (disconnected from bus)
Aug  9 12:51:09 laptop-erik lightdm: pam_unix(lightdm:session): session closed for user erik
Aug  9 12:51:14 laptop-erik lightdm: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory
Aug  9 12:51:14 laptop-erik lightdm: PAM adding faulty module: pam_kwallet.so
Aug  9 12:51:14 laptop-erik lightdm: PAM unable to dlopen(pam_kwallet5.so): /lib/security/pam_kwallet5.so: cannot open shared object file: No such file or directory
Aug  9 12:51:14 laptop-erik lightdm: PAM adding faulty module: pam_kwallet5.so
Aug  9 12:51:14 laptop-erik lightdm: pam_unix(lightdm-greeter:session): session opened for user lightdm by (uid=0)
Aug  9 12:51:14 laptop-erik lightdm: (pam_mount.c:477): warning: could not obtain password interactively either
Aug  9 12:51:14 laptop-erik lightdm: (mount.c:72): Messages from underlying mount program:
Aug  9 12:51:14 laptop-erik lightdm: (mount.c:76): mount error(13): Permission denied
Aug  9 12:51:14 laptop-erik lightdm: (mount.c:76): Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)
Aug  9 12:51:14 laptop-erik lightdm: (pam_mount.c:522): mount of backup failed
Aug  9 12:51:15 laptop-erik lightdm: (mount.c:72): Messages from underlying mount program:
Aug  9 12:51:15 laptop-erik lightdm: (mount.c:76): mount error(13): Permission denied
Aug  9 12:51:15 laptop-erik lightdm: (mount.c:76): Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)
Aug  9 12:51:15 laptop-erik lightdm: (pam_mount.c:522): mount of documents failed
Aug  9 12:51:15 laptop-erik lightdm: (mount.c:72): Messages from underlying mount program:
Aug  9 12:51:15 laptop-erik lightdm: (mount.c:76): mount error(13): Permission denied
Aug  9 12:51:15 laptop-erik lightdm: (mount.c:76): Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)
Aug  9 12:51:15 laptop-erik lightdm: (pam_mount.c:522): mount of download failed
Aug  9 12:51:15 laptop-erik lightdm: (mount.c:72): Messages from underlying mount program:
Aug  9 12:51:15 laptop-erik lightdm: (mount.c:76): mount error(13): Permission denied
Aug  9 12:51:15 laptop-erik lightdm: (mount.c:76): Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)
Aug  9 12:51:15 laptop-erik lightdm: (pam_mount.c:522): mount of fax failed
Aug  9 12:51:15 laptop-erik lightdm: (mount.c:72): Messages from underlying mount program:
Aug  9 12:51:15 laptop-erik lightdm: (mount.c:76): mount error(13): Permission denied
Aug  9 12:51:15 laptop-erik lightdm: (mount.c:76): Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)
Aug  9 12:51:15 laptop-erik lightdm: (pam_mount.c:522): mount of music failed
Aug  9 12:51:15 laptop-erik lightdm: (mount.c:72): Messages from underlying mount program:
Aug  9 12:51:15 laptop-erik lightdm: (mount.c:76): mount error(13): Permission denied
Aug  9 12:51:15 laptop-erik lightdm: (mount.c:76): Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)
Aug  9 12:51:15 laptop-erik lightdm: (pam_mount.c:522): mount of photo failed
Aug  9 12:51:15 laptop-erik lightdm: (mount.c:72): Messages from underlying mount program:
Aug  9 12:51:15 laptop-erik lightdm: (mount.c:76): mount error(13): Permission denied
Aug  9 12:51:15 laptop-erik lightdm: (mount.c:76): Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)
Aug  9 12:51:15 laptop-erik lightdm: (pam_mount.c:522): mount of scans failed
Aug  9 12:51:15 laptop-erik lightdm: (mount.c:72): Messages from underlying mount program:
Aug  9 12:51:15 laptop-erik lightdm: (mount.c:76): mount error(13): Permission denied
Aug  9 12:51:15 laptop-erik lightdm: (mount.c:76): Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)
Aug  9 12:51:15 laptop-erik lightdm: (pam_mount.c:522): mount of video failed
Aug  9 12:51:15 laptop-erik lightdm: (mount.c:72): Messages from underlying mount program:
Aug  9 12:51:15 laptop-erik lightdm: (mount.c:76): mount error(13): Permission denied
Aug  9 12:51:15 laptop-erik lightdm: (mount.c:76): Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)
Aug  9 12:51:15 laptop-erik lightdm: (pam_mount.c:522): mount of web failed
Aug  9 12:51:15 laptop-erik lightdm: (pam_mount.c:477): warning: could not obtain password interactively either
Aug  9 12:51:15 laptop-erik systemd-logind[867]: New session c5 of user lightdm.
Aug  9 12:51:15 laptop-erik systemd: pam_unix(systemd-user:session): session opened for user lightdm by (uid=0)
Aug  9 12:51:16 laptop-erik lightdm: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory
Aug  9 12:51:16 laptop-erik lightdm: PAM adding faulty module: pam_kwallet.so
Aug  9 12:51:16 laptop-erik lightdm: PAM unable to dlopen(pam_kwallet5.so): /lib/security/pam_kwallet5.so: cannot open shared object file: No such file or directory
Aug  9 12:51:16 laptop-erik lightdm: PAM adding faulty module: pam_kwallet5.so
Aug  9 12:51:16 laptop-erik lightdm: pam_succeed_if(lightdm:auth): requirement "user ingroup nopasswdlogin" not met by user "erik"
Aug  9 12:51:20 laptop-erik lightdm: pam_unix(lightdm:session): session opened for user erik by (uid=0)
Aug  9 12:51:20 laptop-erik systemd-logind[867]: Removed session c5.
Aug  9 12:51:20 laptop-erik systemd: pam_unix(systemd-user:session): session closed for user lightdm
Aug  9 12:51:21 laptop-erik systemd-logind[867]: New session c6 of user erik.
Aug  9 12:51:22 laptop-erik polkitd(authority=local): Registered Authentication Agent for unix-session:c6 (system bus name :1.124 [/usr/lib/policykit-1-gnome/polkit-gnome-authentication-agent-1], object path /org/gnome/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8)
Aug  9 12:51:31 laptop-erik smbd: pam_unix(samba:session): session closed for user nobody
ehoitinga

Re: Slow write speeds to Synology NAS shares using pam_mount.

Post by ehoitinga »

Ok,

I configured pam_mount as it should.

Contents of the masterfile in /etc/security:

Code: Select all

<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE pam_mount SYSTEM "pam_mount.conf.xml.dtd">
<pam_mount>
  <!-- Disable debugging 
  -->
  <debug
  		enable="0" 
  />

  <luserconf name=".pam_mount.conf.xml" />

  <!-- All options listed in allow *may* appear in the option list of per-user volume mounts.
       These options do not apply to the master file.
  -->
  <mntoptions 
  		allow="workgroup,nosuid,nodev,nofail,vers,uid,gid,dir_mode,file_mode" 
  />

  <!-- All options listed in require must appear in the option list of per-user volume mounts.
       These options also apply to the master file.
  -->
  <mntoptions
  		require="nosuid,nodev,nofail" 
  />

  <!-- Programs exist that do not terminate when the session is closed. pam_mount can be configured 
       to kill these processes and optionally wait before sending signals. -->
  <logout 
  		wait="0" hup="0" term="yes" kill="0" 
  />

  <!-- Controls automatic creation and removal of mountpoints.
  -->
  <mkmountpoint enable="1" remove="true" />
</pam_mount>
The file .pam_mount.conf.xml in my home directory /home/erik contains:

Code: Select all

<pam_mount>
  <!-- Map some shares residing on the NAS-SERVER to the users home directory
  -->
  <volume
		options="workgroup=HOME,nosuid,nodev,nofail,vers=3.0,uid=%(USERUID),gid=%(USERGID),dir_mode=0750,file_mode=0640"
		user="*"
		fstype="cifs"
		server="192.168.1.248"
		path="backup"
		mountpoint="/home/erik/Backup"
  />
  <volume
		options="workgroup=HOME,nosuid,nodev,nofail,vers=3.0,uid=%(USERUID),gid=%(USERGID),dir_mode=0750,file_mode=0640"
		user="*"
		fstype="cifs"
		server="192.168.1.248"
		path="documents"
		mountpoint="/home/erik/Documents"
  />
  <volume
		options="workgroup=HOME,nosuid,nodev,nofail,vers=3.0,uid=%(USERUID),gid=%(USERGID),dir_mode=0750,file_mode=0640"
		user="*"
		fstype="cifs"
		server="192.168.1.248"
		path="download"
		mountpoint="/home/erik/Downloads"
  />
  <volume
		options="workgroup=HOME,nosuid,nodev,nofail,vers=3.0,uid=%(USERUID),gid=%(USERGID),dir_mode=0750,file_mode=0640"
		user="*"
		fstype="cifs"
		server="192.168.1.248"
		path="fax"
		mountpoint="/home/erik/Fax"
  />
  <volume
		options="workgroup=HOME,nosuid,nodev,nofail,vers=3.0,uid=%(USERUID),gid=%(USERGID),dir_mode=0750,file_mode=0640"
		user="*"
		fstype="cifs"
		server="192.168.1.248"
		path="music"
		mountpoint="/home/erik/Music"
  />
  <volume
		options="workgroup=HOME,nosuid,nodev,nofail,vers=3.0,uid=%(USERUID),gid=%(USERGID),dir_mode=0750,file_mode=0640"
		user="*"
		fstype="cifs"
		server="192.168.1.248"
		path="photo"
		mountpoint="/home/erik/Pictures"
  />
  <volume
		options="workgroup=HOME,nosuid,nodev,nofail,vers=3.0,uid=%(USERUID),gid=%(USERGID),dir_mode=0750,file_mode=0640"
		user="*"
		fstype="cifs"
		server="192.168.1.248"
		path="scans"
		mountpoint="/home/erik/Scans"
  />
  <volume
		options="workgroup=HOME,nosuid,nodev,nofail,vers=3.0,uid=%(USERUID),gid=%(USERGID),dir_mode=0750,file_mode=0640"
		user="*"
		fstype="cifs"
		server="192.168.1.248"
		path="video"
		mountpoint="/home/erik/Videos"
  />
  <volume
		options="workgroup=HOME,nosuid,nodev,nofail,vers=3.0,uid=%(USERUID),gid=%(USERGID),dir_mode=0750,file_mode=0640"
		user="*"
		fstype="cifs"
		server="192.168.1.248"
		path="web"
		mountpoint="/home/erik/Websites"
  />
</pam_mount>
The shares are mounted but the read & write speed and LibreOffice problems as stated in my first post are still there.

The only things that bother me are the error messages concerning "pam_kwallet.so":

Code: Select all

Aug  9 13:19:10 laptop-erik polkitd(authority=local): Unregistered Authentication Agent for unix-session:c8 (system bus name :1.155, object path /org/gnome/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) (disconnected from bus)
Aug  9 13:19:11 laptop-erik lightdm: pam_unix(lightdm:session): session closed for user erik
Aug  9 13:19:16 laptop-erik lightdm: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory
Aug  9 13:19:16 laptop-erik lightdm: PAM adding faulty module: pam_kwallet.so
Aug  9 13:19:16 laptop-erik lightdm: PAM unable to dlopen(pam_kwallet5.so): /lib/security/pam_kwallet5.so: cannot open shared object file: No such file or directory
Aug  9 13:19:16 laptop-erik lightdm: PAM adding faulty module: pam_kwallet5.so
Aug  9 13:19:16 laptop-erik lightdm: pam_unix(lightdm-greeter:session): session opened for user lightdm by (uid=0)
Aug  9 13:19:16 laptop-erik systemd-logind[867]: New session c9 of user lightdm.
Aug  9 13:19:16 laptop-erik systemd: pam_unix(systemd-user:session): session opened for user lightdm by (uid=0)
Aug  9 13:19:16 laptop-erik lightdm: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory
Aug  9 13:19:16 laptop-erik lightdm: PAM adding faulty module: pam_kwallet.so
Aug  9 13:19:16 laptop-erik lightdm: PAM unable to dlopen(pam_kwallet5.so): /lib/security/pam_kwallet5.so: cannot open shared object file: No such file or directory
Aug  9 13:19:16 laptop-erik lightdm: PAM adding faulty module: pam_kwallet5.so
Aug  9 13:19:16 laptop-erik lightdm: pam_succeed_if(lightdm:auth): requirement "user ingroup nopasswdlogin" not met by user "erik"
Aug  9 13:19:21 laptop-erik lightdm: pam_unix(lightdm:session): session opened for user erik by (uid=0)
Aug  9 13:19:21 laptop-erik systemd-logind[867]: Removed session c9.
Aug  9 13:19:21 laptop-erik systemd: pam_unix(systemd-user:session): session closed for user lightdm
Aug  9 13:19:22 laptop-erik systemd-logind[867]: New session c10 of user erik.
Aug  9 13:19:23 laptop-erik polkitd(authority=local): Registered Authentication Agent for unix-session:c10 (system bus name :1.185 [/usr/lib/policykit-1-gnome/polkit-gnome-authentication-agent-1], object path /org/gnome/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8)
Aug  9 13:19:35 laptop-erik smbd: pam_unix(samba:session): session closed for user nobody
and the CIFS mount failed messages in the output of dmesg | grep -i failed. As far as I know the CIFS mount code means permission denied.

Code: Select all

[  935.879850] CIFS VFS: cifs_mount failed w/return code = -13
[  936.042434] CIFS VFS: cifs_mount failed w/return code = -13
[  936.319441] CIFS VFS: cifs_mount failed w/return code = -13
[  936.552980] CIFS VFS: cifs_mount failed w/return code = -13
[  936.753321] CIFS VFS: cifs_mount failed w/return code = -13
[  936.908627] CIFS VFS: cifs_mount failed w/return code = -13
[  937.215318] CIFS VFS: cifs_mount failed w/return code = -13
[  937.391758] CIFS VFS: cifs_mount failed w/return code = -13
[  937.587454] CIFS VFS: cifs_mount failed w/return code = -13
[  989.884146] CIFS VFS: cifs_mount failed w/return code = -13
[  990.012388] CIFS VFS: cifs_mount failed w/return code = -13
[  990.141258] CIFS VFS: cifs_mount failed w/return code = -13
[  990.270500] CIFS VFS: cifs_mount failed w/return code = -13
[  990.399493] CIFS VFS: cifs_mount failed w/return code = -13
[  990.528442] CIFS VFS: cifs_mount failed w/return code = -13
[  990.659249] CIFS VFS: cifs_mount failed w/return code = -13
[  990.787462] CIFS VFS: cifs_mount failed w/return code = -13
[  990.918996] CIFS VFS: cifs_mount failed w/return code = -13
I am a bit puzzled here. The shares however are properly mounted an reachable. Read & write speed and LibreOffice problems as stated in my first post are still there.

Any input is welcome.

Thanks
ehoitinga

Re: Slow write speeds to Synology NAS shares using pam_mount.

Post by ehoitinga »

Hi,

In the end I solved the problem myself. It turned out to be a samba setting on my nas server.

I had to switch the option "Enable SMB2 leases" to on and all the problems as stated in my first post were gone.

Code: Select all

Enable SMB2 lease: Enabling this option allows more SMB2-related settings to fine-tune the client caching mechanism provided by Opportunistic Locking.
I am sorry :oops: that I have bothered you

Erik
Locked

Return to “Networking”