You are not logged in.

Dear visitor, welcome to KDE-Forum.org. If this is your first visit here, please read the Help. It explains in detail how this page works. To use all features of this page, you should consider registering. Please use the registration form, to register here or read more information about the registration process. If you are already registered, please login here.

1

Friday, May 20th 2005, 6:11am

Samba Volume Experiences Significant Delay (Miinutes) Using Konqueror

I don't know if the issue below is a Colinux issue, a SAMBA issue or a Konqueror issue, but I would appreciate any comments that anyone has on the following issue.

I am running Debian with KDE 3.3.0 on top of colinux.

I have mounted the e: drive from my Windows XP Home host system inside colinux 0.6.2 Colinux 0.6.2 is running in a reliable and healthy fashion. The mount is performed using the samba client within Debian/KDE.


I perform a mount operation from the KDE desktop icon for the e: drive (right click icon select mount).

Mount seems to work fine, but when I right click the icon and select open to browse the drive with the Konqueror web/file browser, I experience an extended delay of several minutes before the file list appears within Konqueror.

I can look at the file list for the mounted SAMBA volume (i.e. the e: drive) with bash without delay.

What is causing this extended delay?

I noticed the following error messages

2005/05/18 17:31:19, 0] tdb/tdbutil.c:tdb_log(725)
tdb(/var/run/samba/gencache.tdb): tdb_lock failed on list 21 ltype=0 (Bad file descriptor)
[2005/05/18 17:31:19, 0] tdb/tdbutil.c:tdb_log(725)
tdb(/var/run/samba/gencache.tdb): tdb_lock failed on list 21 ltype=1 (Bad file descriptor)
[2005/05/18 17:31:20, 0] tdb/tdbutil.c:tdb_log(725)
tdb(/var/run/samba/gencache.tdb): tdb_lock failed on list 21 ltype=1 (Bad file descriptor)

What is causing the above errors and how do I correct these errors?

The timestamp on the errors seem to correlate pretty well with the time when I performed the samba mount operation.

/Ross

anda_skoa

Professional

Posts: 1,273

Location: Graz, Austria

Occupation: Software Developer

  • Send private message

2

Friday, May 20th 2005, 11:18am

Do you also get this delay when listing the mounted directory from the shell?

Cheers,
_
Qt/KDE Developer
Debian User

3

Friday, May 20th 2005, 4:23pm

No I don't seem to experience the same delay when accessing the mounted SAMBA volume from within the shell (bash).

/Ross

4

Friday, May 20th 2005, 9:50pm

I spent a little time testing mount operations from the bash shell and from
the KDE desktop.

Here's what I found:

i. The mount command from Bash works reliably (every time).
ii. When I right click the SMB volume on the KDE desktop the mount
operation performed by Bash is reflected on the
KDE desktop icon (the mount option has changed to unmount), so the
mount operation is working properly and the KDE desktop environment
recognizes the mount.
iii. When I perform an ls on the mounted volume (ls /mnt/maxtor), it
displays immediately (file names only).
iv. When I click on the desktop icon for the same volume, I experience the
delay I described previously.
v. the delay only occurs on the first access to the icon, after that
normal operation occurs. If I close the icon window
and reopen after the first successful browse of the volume, and then
re-open the window no problem occurs

My conclusion are as follows:

1. Mount operation is working OK
2. There is a difference in SMB traffic between using the bash shell and
using the Konqueor graphical browser.
3. It seems like some kind of timeout is in place on the first access by
Konqueror to the mounted SMB volume. Once timeout occurs, the issue
goes away

Does the colinux kernal get involved in any way with Samba?
If not this may not be a colinux issue

I am running Windows XP Home on the SMB FS server side (host os for
colinux). Are there any know limitations in Windows XP Home implementation of SMB FS that might account for this behaviour?

/Ross

anda_skoa

Professional

Posts: 1,273

Location: Graz, Austria

Occupation: Software Developer

  • Send private message

5

Saturday, May 21st 2005, 11:39am

Hmm.

As the SMB operation are handled by smbfs Konqueror also uses the file system API like ls.

Can you check if you get that delay when opening Konqueror on another local filesystem path, e.g. /home?

Cheers,
_
Qt/KDE Developer
Debian User

6

Saturday, May 21st 2005, 5:43pm

There are no delays exhibited by Konqueror when accessing files in
(co)Linux root fs.

The problem is specific to SAMBA volues.

Is it possible for you to outline the API calls and parameters used by
Konqueror when accessing a SAMBA volume, and I will post a
question to one of the Samba discussion groups about this issue,
and see what they have to say?

/Ross

This post has been edited 1 times, last edit by "rossmac" (May 21st 2005, 5:44pm)


anda_skoa

Professional

Posts: 1,273

Location: Graz, Austria

Occupation: Software Developer

  • Send private message

7

Saturday, May 21st 2005, 8:09pm

Quoted

Originally posted by rossmac
There are no delays exhibited by Konqueror when accessing files in
(co)Linux root fs.

Hmm, ok. Then it is not the spawing of the file IO slave.

Quoted


The problem is specific to SAMBA volues.

Just to make sure: Konqueror is using a local file path there (file:/mountpoint) not connection itself (smb://host/share)

Quoted


Is it possible for you to outline the API calls and parameters used by
Konqueror when accessing a SAMBA volume, and I will post a
question to one of the Samba discussion groups about this issue,
and see what they have to say?


Unfortunately I don't know the exact details. I assume it uses the standard POSIX API.

Do you have any interesting messages in .xsession-errors?
Anything being logged when the debug area for kio_file is enabled in kdebugdialog?

Cheers,
_
Qt/KDE Developer
Debian User

8

Saturday, May 21st 2005, 8:15pm

The path that I am accessing with Konqueror and ls (after a successful
mount operation) is:

/mnt/maxtor

/Ross