Greetings.
I installed all updates on my Leap 42.3 box Friday. Since then, I’ve been unable to copy files to and from the machine via the directories shared with Samba.
I’m convinced that the issue is not hardware, because I can successfully access the files over the network with rsync and smbcopy. Nor is the problem with the client machine (also running Leap 42.3 and updated Friday as well), as it fails in the same way with a second machine running Debian Jesse. A Windows 10 machine also fails.
On the Linux clients, the mount appears normal, but attempts to copy files from the share fail with “cannot open ‘[filename]’ for reading: Input/output error” and copying to the share fails with "cannot create regular file ‘[filename]’: Input/output error
On the Windows client, the share mounts, but any attempt to access it gives a “Windows can’t access this disc” message which suggests the disc “might be corrupt.”
The relevant sections of the server’s smb.conf are:
[global]
workgroup = TEAM-H
printing = cups
printcap name = cups
printcap cache time = 750
cups options = raw
# printer admin = @ntadmin, root, administrator
username map = /etc/samba/smbusers
map to guest = Bad User
include = /etc/samba/dhcp.conf
logon path = \\%L\profiles\.msprofile
logon home = \\%L\%U\.9xprofile
logon drive = P:
security = user
ldap idmap suffix = ou=Idmap
ldap machine suffix = ou=Computers
ldap suffix = dc=example,dc=com
passdb backend = smbpasswd
encrypt passwords = Yes
add machine script = /usr/sbin/useradd -c Machine -d /var/lib/nobody -s /bin/false %m$
domain logons = No
domain master = Yes
local master = Yes
os level = 65
preferred master = Yes
wins support = No
usershare max shares = 100
usershare allow guests = Yes
unix extensions = Yes
ldap admin dn =
netbios name = TIRA-CHAN
[everything]
comment = All shared files on this server
path = /media/sharedData/
writeable = yes
read only = No
follow symlinks = Yes
wide links = Yes
#inherit acls = Yes
The clients are mounting the share with:
//tira-chan/files /home/solop/Network/Files cifs credentials=/etc/samba/creds,uid=solop,gid=users 0 0
Any suggestions? Ones that don’t involve changing to a different server protocol?
Thanks in advance!