CIFS: Navigating directories in DFS shares buggy

Bug #134080 reported by John Anderson
38
This bug affects 3 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Undecided
Unassigned
samba (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: smbfs

After upgrading our Windows fileservers to 2003 DFS we get strange behavior when mouting shares.

The initial folder below the share appears three levels deep. For example to get to share \\server\public\stuff we must cd to public/stuff/stuff/stuff.

This does not happen on our non-DFS servers, nor does it happen if we use FUSE or konq, which are using libsmbclient.

Tags: kj-triage
Revision history for this message
Mathias Gug (mathiaz) wrote : Re: [Bug 134080] Navigating directories for DFS shares buggy

Thanks for reporting the bug and help to make Ubuntu better.

Could you specify which version of samba you are running ? Also, did you
try to use the cifs client instead of smbfs ?

 status incomplete

Changed in samba:
status: New → Incomplete
Revision history for this message
John Anderson (john-e-anderson) wrote :

My samba version is 3.0.24-2ubuntu1. I tried cifs, and that results in
the same behavior.

Revision history for this message
Launchpad Janitor (janitor) wrote : Re: Navigating directories for DFS shares buggy

[Expired for samba (Ubuntu) because there has been no activity for 60 days.]

Mathias Gug (mathiaz)
Changed in samba:
status: Invalid → Incomplete
Revision history for this message
John Anderson (john-e-anderson) wrote :

I'm still getting this behavior in hardy on a new machine with cifs and smbfs.

Samba 3.0.28-4ubuntu1

Changed in samba:
status: Incomplete → Confirmed
Revision history for this message
kevin murray (kjmurray) wrote :

I have seen this too when introducing a windows 2003 DFS fileserver on our office network.

The initial folder below the share appears three levels deep, as stated above. Passing the third level gives an 'Object is Remote' error. Also, you could give any non-existent folder name in the first three levels and the initial folder was returned as that imaginary folder's content. We were mounting this share using cifs on a hardy client box. We were getting the same result for gentoo, fedora9 (with all the latest patches), and bsd clients too.

We could see everything properly via smbclient.

What we found is we that we needed to use the the actual name of the folder on the windows server that was shared to connect properly, not the windows share name for the folder we were given by our DFS admin. Not that this should be the case, but we needed this to work soon. Smbclient was able to work with the share name, and 'showconnect' showed the actual name of the of the share name we supplied.

Something is stopping the sharename from being known by the clients when connecting to windows 2003 DFS from cifs clients.

..can give more info from colleagues if needed..

Revision history for this message
Se6 (se6astien) wrote :

Same problem here. That is due to mount.cifs.
See that thread: http://lists.samba.org/archive/linux-cifs-client/2007-March/001879.html

Seb.

Revision history for this message
Se6 (se6astien) wrote :

Here: http://lists.samba.org/archive/linux-cifs-client/2008-July/003110.html it says it should work soon or later... kernel >= 2.6.26.

Seb.

Revision history for this message
Chuck Short (zulcss) wrote :

This should be fixed in intrepid now

Changed in samba:
status: Confirmed → Fix Released
Revision history for this message
John Anderson (john-e-anderson) wrote :

Could I get some info on how this was fixed? New upstream Samba?

Revision history for this message
dsmith1974 (dsmith1974) wrote :

This does not appear to be fixed in the 8.10 Intreped release either. I still get the remote object error when attempting to cd into directories on a DFS file-system.

Regards,

Duncan

Revision history for this message
John Anderson (john-e-anderson) wrote :

I'm setting this back to confirmed as I am still seeing this issue, as is dsmith1974. I don't think it is fixed.

Changed in samba:
status: Fix Released → Confirmed
Revision history for this message
Chris Higgins (chrishig) wrote :

I'm running Jaunty Alpha 5 (fresh install) - and can confirm that I still see this today.

Revision history for this message
Thierry Carrez (ttx) wrote :

DFS support in kernel CIFS moved from experimental to supported for 2.6.29, and there are quite a few patches since the 2.6.28 we use in Jaunty, especially a "[CIFS] make sure that DFS pathnames are properly formed" that might explain this.

Reassigning to kernel, since it works alright in smbclient...

Changed in samba:
status: Confirmed → Invalid
Revision history for this message
kernel-janitor (kernel-janitor) wrote :

Hi john-e-anderson,

This bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? Can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you run the following command from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux-image-`uname -r` 134080

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

tags: added: needs-kernel-logs
tags: added: needs-upstream-testing
tags: added: kj-triage
Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
epicurea (suknat) wrote :

I think I am having a similar problem:

I am trying to mount 3 remote shares via /etc/fstab using:
//server-name/share /smb/somefolder smbfs auto,credentials=smbcredentials,uid=XXX,gid=XXX,umask=000 0 0

Two of these mount just fine while a 3rd does not, causing nautilus to hang and an ls on /smb to give a segmentation fault. It is possible that this is a DFS share - as the other two share points (which work) are on the same server.

Using nautilus to load the problematic share using:
smb://server-name/share/folder
authenticates and works just fine.

Using Intrepid and all available updates as of today.

Thanks.

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Could you test and confirm with the more recent 9.10 Karmic Alpha release? http://cdimage.ubuntu.com/releases/karmic . Thanks.

Changed in linux (Ubuntu):
status: Incomplete → New
status: New → Incomplete
Revision history for this message
Marc G. (marc-gu) wrote :

I had a similar problem (see duplicate Bug #320212). I tested with the final release of Karmic and the problem is still present.

I can mount the windows share with :
sudo mount.cifs //192.168.2.15/data /mnt/data -o user=workgroup/username,uid=marc,gid=marc

I can see folders in the share but I can't access them, I get the error "resource temporarily unavailable". I can unmount the share without any problem.

With Jaunty, I was able to access the share with nautilus, but with Karmic it's no longer possible. The only way to access the share is using smbclient which work perfectly.

mount.cifs version : 1.12-3.4.0

Revision history for this message
Marc G. (marc-gu) wrote : apport-collect data

Architecture: amd64
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: marc 2615 F.... pulseaudio
 /dev/snd/pcmC0D0p: marc 2615 F...m pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xfebfc000 irq 21'
   Mixer name : 'SigmaTel STAC9205'
   Components : 'HDA:838476a0,102801f1,00100204 HDA:14f12c06,14f1000f,00100000'
   Controls : 19
   Simple ctrls : 11
DistroRelease: Ubuntu 9.10
HibernationDevice: RESUME=UUID=f89014a5-108b-45bd-8a9b-d68d83d4cfbb
MachineType: Dell Inc. Inspiron 1520
NonfreeKernelModules: nvidia
Package: linux-image-2.6.32-999-generic 2.6.32-999.200911061000
PackageArchitecture: amd64
ProcCmdLine: BOOT_IMAGE=/vmlinuz-2.6.32-999-generic root=/dev/mapper/marc--laptop-root ro quiet splash
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, no user)
 LANG=fr_CA.UTF-8
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: yes
Uname: Linux 2.6.32-999-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare vboxusers
dmi.bios.date: 07/11/2008
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A09
dmi.board.name: 0UW306
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrA09:bd07/11/2008:svnDellInc.:pnInspiron1520:pvr:rvnDellInc.:rn0UW306:rvr:cvnDellInc.:ct8:cvr:
dmi.product.name: Inspiron 1520
dmi.sys.vendor: Dell Inc.

Revision history for this message
Marc G. (marc-gu) wrote : AlsaDevices.txt
Revision history for this message
Marc G. (marc-gu) wrote : AplayDevices.txt
Revision history for this message
Marc G. (marc-gu) wrote : BootDmesg.txt
Revision history for this message
Marc G. (marc-gu) wrote : Card0.Amixer.values.txt
Revision history for this message
Marc G. (marc-gu) wrote : Card0.Codecs.codec.0.txt
Revision history for this message
Marc G. (marc-gu) wrote : Card0.Codecs.codec.1.txt
Revision history for this message
Marc G. (marc-gu) wrote : CurrentDmesg.txt
Revision history for this message
Marc G. (marc-gu) wrote : Dependencies.txt
Revision history for this message
Marc G. (marc-gu) wrote : IwConfig.txt
Revision history for this message
Marc G. (marc-gu) wrote : Lspci.txt
Revision history for this message
Marc G. (marc-gu) wrote : Lsusb.txt
Revision history for this message
Marc G. (marc-gu) wrote : PciMultimedia.txt
Revision history for this message
Marc G. (marc-gu) wrote : ProcCpuinfo.txt
Revision history for this message
Marc G. (marc-gu) wrote : ProcInterrupts.txt
Revision history for this message
Marc G. (marc-gu) wrote : ProcModules.txt
Revision history for this message
Marc G. (marc-gu) wrote : UdevDb.txt
Revision history for this message
Marc G. (marc-gu) wrote : UdevLog.txt
Revision history for this message
Marc G. (marc-gu) wrote : WifiSyslog.txt
Revision history for this message
Marc G. (marc-gu) wrote : XsessionErrors.txt
Changed in linux (Ubuntu):
status: Incomplete → New
tags: added: apport-collected
tags: removed: apport-collected needs-kernel-logs needs-upstream-testing
Revision history for this message
Se6 (se6astien) wrote :

Looking around in the Samba linux-cifs-client archives, it seems that to get DFS working, you need to first install the package keyutils and to add to /etc/request-key.conf something like:

create cifs.spnego * * /usr/local/sbin/cifs.upcall -c %k
create dns_resolver * * /usr/local/sbin/cifs.upcall %k

The second line seems important here, the first one is for kerberos.
man cifs.upcall to get more info.

Could someone with Karmic and access to a Windows DFS server try that?

Se6.

Revision history for this message
Marc G. (marc-gu) wrote :

I installed the package keyutils and founded that the two lines were already present in /etc/request-key.

But the installation of keyutils resolved my problem, now I'm able to access to a Windows DFS share in command line. Thanks a lot !

p.s. mounting directly in nautilus is still buggy.

Se6 (se6astien)
Changed in samba (Ubuntu):
status: Invalid → In Progress
status: In Progress → Confirmed
Revision history for this message
Christophe (marbacher) wrote :

I've the same issue on a computer with Ubuntu 9.10 Karmic trying to access a NAS that presents standalone DFS. Using "mount -t cifs" at the command line, I can access the DFS target, but using the Nautilus menu "connect to a server" it fails back in SMB (I guess).

Regards,
Christophe

Revision history for this message
Thierry Carrez (ttx) wrote :

Marc G., Se6: Your issue is different from the original poster one (it's bug 300221, which is now fixed in lucid).

Changed in samba (Ubuntu):
status: Confirmed → Invalid
Revision history for this message
Brad Figg (brad-figg) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 134080

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
lolow (ldrouet) wrote :

I have the same problem (3 level deep).
kernel 2.6.38-11
ubuntu natty

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.