Redundant directory levels with cifs

bingo · 02-28-2007, 01:11 PM

I am running Slacware 11.0 with a custom 2.6.20 kernel, and the latest stable Samba version. Just recently, I started having permission issues using smbfs on my work network. After some research, I decided to try the newer cifs, which is working well with just 1 minor issue. On only 1 of my mount-points, the initial directory tree is redundant 3X. Hopefully this helps... If my mount-point is X, and I navigate to directory Y within the mount, it looks exactly like X. There are 3 levels of this, then the directories navigate as normal. The tree then looks like: /mnt/X/X/X/Y/Z..., where Y,Z is the directory I'm trying to navigate to directly from the original mount-point X. Here is my fstab:

Code:

//fileserver/fileserver	/mnt/fileserver	cifs	noauto,user=me,file_mode=0777,dir_mode=0777,rw	0   0

Thanks in advance for the help! ...Steve

jschiwal · 02-28-2007, 02:34 PM

Are you saying that that is the way it appears for the mounted share, but the directory structure of the filesystem doesn't show this?

bingo · 02-28-2007, 04:16 PM

Sorry I didn't explain this very well. The actual file structure is /X/Y/Z, but what I see is /X/X/X/Y/Z. Specifically....

- /mnt/fileserver has 12 directories and 4 files in it (correct)
- /mnt/fileserver/(any directory) shows the same 12 directories and 4 files (incorrect)
- /mnt/fileserver/(any directory)/(any directory) shows the same 12 directories and 4 files (incorrect)
- /mnt/fileserver/(any directory)/(any directory)/(any directory) shows the correct contents for the last directory, but the path is incorrect (it should be /mnt/fileserver/(any directory))

Any ideas from that? ...Steve

jschiwal · 02-28-2007, 05:47 PM

If is was a recursive loop I would suspect a link.

You might want to look at the output of "smbtree" and "mount" on the server.
Look at the long listing as well. With NFS you can't have a subdirectory of a shared directory also shared. I wonder if there is something like that is going on.

The other thing I can think of is that you can have a chroot situation where the directory structure in samba looks one way before the chroot, but in a subsequent subshell, it looks differently.

Also, check if the filesystem is corrupted.

You may need to restart samba. Maybe the situation will be corrected.