SooHow Cheng
asked on
What went wrong with this CIFS share mapping in Linux?
This is using SuSE Enterprise server SLES12. There is a mapping for this CIFS share on the server.
//172.29.53.138/data cifs 233G 92G 142G 40% /mnt/172.29.53.138
In the "mount" command, see how this CIFS mapping established,
//172.29.53.138/data on /mnt/172.29.53.138 type cifs (rw,relatime,vers=1.0,cache=strict,username=chapman,uid=1015,forceuid,gid=0,noforcegid,addr=172.29.53.138,file_mode=0755,dir_mode=0755,soft,nounix,serverino,mapposix,rsize=61440,wsize=65536,bsize=1048576,echo_interval=60,actimeo=1)
Recently, see this error messages from /var/log/messages,
2021-05-24T10:07:48.691737+08:00 ssin3empacXX kernel: [13722631.632626] CIFS VFS: \\172.29.53.138 Send error in SessSetup = -13
What went wrong with this CIFS mapping?
Thanks in advance
//172.29.53.138/data cifs 233G 92G 142G 40% /mnt/172.29.53.138
In the "mount" command, see how this CIFS mapping established,
//172.29.53.138/data on /mnt/172.29.53.138 type cifs (rw,relatime,vers=1.0,cache=strict,username=chapman,uid=1015,forceuid,gid=0,noforcegid,addr=172.29.53.138,file_mode=0755,dir_mode=0755,soft,nounix,serverino,mapposix,rsize=61440,wsize=65536,bsize=1048576,echo_interval=60,actimeo=1)
Recently, see this error messages from /var/log/messages,
2021-05-24T10:07:48.691737+08:00 ssin3empacXX kernel: [13722631.632626] CIFS VFS: \\172.29.53.138 Send error in SessSetup = -13
What went wrong with this CIFS mapping?
Thanks in advance
ASKER
Hi Seth,
This is working in the past. I will check the credentials.
This is working in the past. I will check the credentials.
Can you ping the host 172.29.53.138?
Can you confirm it did not lose the setting, or someone mocked around with the software firewall knocking access out?
In issues, I find it helpful to confirm the source is there and not generating errors.
Updates?
Can you confirm it did not lose the setting, or someone mocked around with the software firewall knocking access out?
In issues, I find it helpful to confirm the source is there and not generating errors.
Updates?
ASKER
The IP wasn't pingeable while this error occurred. Found out that the storage where this CIFS share located is "off".
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
There were some maintenance jobs for the san storage
was this working before? if so, did someone change something on the target server either at the share or file system level?
if this is the first time trying to mount, make sure the account has proper access to that share
error 13 is permission denied