Red Hat Bugzilla – Bug 200680
if share name and directory name in the share are the same, first instance of cd'ing into the directory goes to share root
Last modified: 2014-06-18 03:35:31 EDT
Description of problem:
I think this started happening during the last couple of samba auto-updates.
First I was forced to change my clients from smbfs to cifs, then the latest
"a" release broke the clients being able to read. Somewhere during that time
this started happening.
The problem: If I have a samba public share (//netfs/public -> /public), and I
have a directory under the share with the same share name (/public/www/public/)
the first time I cd into the directory, it takes me to the root directory of the
For example, I have the directory "temp" in the public directory. I should be
able to get to the directory by doing a "cd /public/www/public/temp/". But that
does not work. Instead I have to do a "cd /public/www/public/www/public/temp".
If it makes a difference, I mount the smb share with autofs.
Version-Release number of selected component (if applicable):
[root@tigger log]# grep samba yum.log
Jul 15 04:39:39 Updated: samba-common.i386 3.0.23-1.fc4
Jul 15 04:39:44 Updated: samba-client.i386 3.0.23-1.fc4
Jul 15 04:51:01 Updated: samba.i386 3.0.23-1.fc4
Jul 27 06:18:58 Updated: samba-common.i386 3.0.23a-1.fc4.1
Jul 27 06:19:24 Updated: samba-client.i386 3.0.23a-1.fc4.1
Jul 27 06:19:35 Updated: samba.i386 3.0.23a-1.fc4.1
Steps to Reproduce:
1. create a share with name X
2. mount the share
3. create a directory under the share www/X
4. cd into the directory "X/www/X"
5. list directory (ls)
root directory of share is shown
contents of directory should be shown
shares are mounted via autofs and are public/guest/writable.
This report targets the FC3 or FC4 products, which have now been EOL'd.
Could you please check that it still applies to a current Fedora release, and
either update the target product or close it ?
This is a CIFS VFS related issue, moving to kernel.
Fedora Core 4 is no longer maintained.
Setting status to "INSUFFICIENT_DATA". If you can reproduce this bug in the
current Fedora release, please reopen this bug and assign it to the
corresponding Fedora version.