smb access almost unusable slow in Dapper compared to Breezy

In fact (at least for me) browsing smb with nautilus is unusable slow, so changing severity to major.

wrong package, changing to gnome-vfs2

What can I do to debug this problem? It often takes 10, 15 seconds to display the contents of a new folder in nautilus and system monitor shows a lot of network traffic (it seems it takes longer if there are more files in this folder) whereas konqueror displays the same folder in under a second, so I assume the smb network is correctly configured (with shares-admin). Preview in nautilus is only local, so that should be no problem.

anything happening here?

Can you check it with the latest Dapper packages? Please reopen the bug if necessary.
Thanks :)

no changes here, still unusable slow :(

Baishampayan,

the issue is not solved (at least not for me). Is there a chance to fix it until the Dapper release?

Frank

I think Ubuntu is flooded with bugs now and there are only a handful people fixing all this myriads of bugs; so, we must help ourselves and provide all the information necessary to identify the problem so that the developers can quickly fix it.

So:
I have a laptop and a desktop system, connected via WLAN. Does anybody have a wired system?

It seems the more files are in a folder the longer it takes to display the content of that folder. Can anyone else confirm this? It's like nautilus is trying to transfer all the files (the actual files, not a description) before it displays the content of that folder.

There is always lots of network traffic when I try to open a folder, so I think it hasn't something to do with the network slowing down or being misconfigured but something is wrong with displaying the content.

If it helps, I can make a Byzanz screencast.

I can confirm it on a wired network environment.

I had the exact same environment with Breezy and no issues, nautilus on Dapper has these issues. So it has to be a change from nautilus-Breezy to nautilus-Dapper.

I'm experiencing extreme slowness with WebDAV+SSL; might be related.

anything happening here?

Frank, has said some comments ago the desktop team is bug flooded, there is hundred of bugs filled a week (a good part of it beeing duplicates and random wishlist) and there is few people working on those, easy to do the maths and figure that people have to prioritize the work. That issue is an upstream one and probably the same on all distro, it would require somebody having a smb use and wanting to work with upstream on it. It's on somewhat on my list but I've still a backlog of around 190 bugs to reply too before. There is a mail on the gnome-vfs upstream list from today with title "Problems with SMB module" so maybe upstream will work on it.

I'm setting the bug as to look on for dapper, but you use an unstable version so try better to try working with upstream if you want to get it fixed quickly. Pinging every few days on the bug is not going to make things faster if people are just overworked which is the case at the moment ...

Sebastien,

I was not aware of this situation, it just seemed to me that the bug got "forgotten". Sorry for that, I'm really not in a hurry!

Frank

Thanks Sebastien, appreciate what you do, we know you work like mad :-)

Just for the record: Tried fedora core 5 and smb browsing via nautilus was quite snappy, so it must be (at least a little bit) Ubuntu-specific.

Nevertheless, interesting news:
I get very slow browsing when I use the following:
Go to Places - Network Servers - Windows Network - netzwerk ...

If I do the following: Places - Connect to Server... and connect via Service type "Windows share" everything is really fast again, even if I use Places - Network Servers - Windows Network afterwards. When I disconnect the share on my Deskop, browsing is slow again.

Frank, maybe you can confirm this?

I am also having the same problem. Yesterday my samba was working fine with 5.10 but as today i upgraded to dapper it is quite slow.

Do any of you have access to that samba server and can check if it is suffering from a high load or millions of smbd processes or something? http://mail.gnome.org/archives/gnome-vfs-list/2006-March/msg00048.html could be related.

Yes, that's it. I checked with SWAT, and I have hundreds of smb processes, and I'm the only user. With Breezy, there are only a handful of open processes.

Applying the patch from http://mail.gnome.org/archives/gnome-vfs-list/2006-March/msg00048.html
should fix this bug. Good news indeed.

I can confirm that the problem here with excessive connections occurs here too and that the patch linked to above fixes the problem.

Could someone attach (a non-HTML-mangled version of) the patch linked above?

Matt, is that ok to upload now or better after the beta freeze?

rubinstein,

sorry I'm a bit late but I can confirm the behavior you have.

frank

Those are some good news, indeed :)

So, has the patch already been applied?
I don't want to push anyone, just trying to close some bugs ;-)

clast

I just noticed this bug after googling for slow network in Dapper. I have the same problem. Local Network browsing is useable but slow, across the wireless network it is pretty close to unusable. If I can help in anyway....

Both machines are using Realtech chipset Belkin cards, but from whats been said this problem is not with the network, but with the GUI.

Dan

This upload has the patch pointed by upstream, could people who noticed smb speed issues comment if that makes it better after restarting their session?

 gnome-vfs2 (2.14.0-0ubuntu2) dapper; urgency=low
 .
   * debian/patches/15_smb_cache_lookup_fix.patch:
     - fix the smb cache lookup, patch from upstream list (Ubuntu: #34203)
   * debian/patches/16_ftp_ls_parse_fix.patch:
     - use atoll instead of atol so the value are not truncated (Ubuntu: #39794)

 gnome-vfs2 (2.14.0-0ubuntu2) dapper; urgency=low

works for me.

it is still rather slow, i don't how it was before the update though!
sometimes the shares can't be displayed the first time you try. i have to hit reload almost everytime im browsing the shares of a remote windows computer.

besides that it's working better than in breezy :)

Just for the info: I use 14 seconds to open a share with 500 folders inside. That is from i doubble click it, till the content is fully shown. (And it is only the first time, guess it is some cache somewhere).

So I will say that browsing a share is usable, and this is over wireless. Ipw2200 card to a slow 600Mhz gateway/server

Marking as fixed. Feel free to reopen if you still have the issue