Package: cifs-utils Version: 2:5.5-1 Severity: important Dear Maintainer,
Also see http://unix.stackexchange.com/questions/164037/mount-cifs-error2-no-such-file-or-directory-when-using-a-prefixpath for a description of this issue. A path that was previously mounted stopped working. Both the following returned an error: mount -t cifs //server/share /mnt/directory -o credentials=/path/to/cifs.credentials,prefixpath=directory --verbose mount -t cifs //server/share/directory /mnt/directory -o credentials=/path/to/cifs.credentials --verbose The response/error message is: mount.cifs kernel mount options: ip=<IP of server>,unc=\\server \share,user=<username>,prefixpath=directory,pass=******** mount error(2): No such file or directory Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) I verified that it was a valid path by mounting the share without the prefixpath: mount -t cifs //server/share /mnt/directory -o credentials=/path/to/cifs.credentials --verbose I was then able to traverse to the directory within the share. This share is on a NetApp SAN. Working with their support, they indicated that the client is attempting to mount //server/share//directory (Note the double slash between the share and the prefixpath.) See also http://unix.stackexchange.com/questions/164037/mount-cifs-error2-no-such-file-or-directory-when-using-a-prefixpath for a description of this issue. -- System Information: Debian Release: 7.8 Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages cifs-utils depends on: ii libc6 2.13-38+deb7u7 ii libkeyutils1 1.5.5-3+deb7u1 ii libkrb5-3 1.10.1+dfsg-5+deb7u3 ii libtalloc2 2.0.7+git20120207-1 ii libwbclient0 2:3.6.6-6+deb7u4 ii samba-common 2:3.6.6-6+deb7u4 Versions of packages cifs-utils recommends: ii keyutils 1.5.5-3+deb7u1 ii winbind 2:3.6.6-6+deb7u4 Versions of packages cifs-utils suggests: ii smbclient 2:3.6.6-6+deb7u4 -- no debconf information -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
