Husain Ali Al-Mohssen
2002-Sep-21 16:44 UTC
[Samba] Samba Very Slow When Using AFS and MS Office (is this a Bug?)
Hi All,
I am having a problem with Samba that seems to be a bug. I say this
because I read the archives and they described a problem similar to mine
and were told that it was a bug in older version of Samba and the latest
version should have it fixed. I am running what is essentially a RH 7.3 on
a 1.4GHz Athon with 1GB or RAM. I compiled Samba 2.2.5 in /opt/samba-2.2.5
and am using the following smb.conf:
[global]
workgroup = FLASH1
interfaces = vmnet1
bind interfaces only = yes
log file = /var/log/samba/log.%m
[homes]
guest ok = no
read only =no
[60GB]
comment = Temporary file space
path = /60GB
read only = no
public = yes
What I am trying to do is to have Samba bind only to the internal network
device so that no one can look @ my samba share from the outside network.
vmnet1 is a VMWare vertual network.
My client is a virtual Windows 2k (sp2) with the modification to the
regestry that allows passwords to be sent in the clear as described by the
Samba documentation.
Now everything is good and fast when I try to access the 60GB share that
is a local disk. The problem is that when I try to access my home
directory things are slow and sometimes files don't showup. In particular,
when I try to access MS Office files things are very very slow. If I copy
the same file to the /60GB partition accessing it through samba is very
fast and normal.
Please note that the AFS partion is already mounted before I login to
Samba from the win2k machine so Samba should just see the files there. I
started nmbd and smbd with the -d 1 option and the log.%m file for the
win2k machine is very big but essentially full of things like:
[2002/09/21 00:01:25, 0] locking/posix.c:posix_fcntl_lock(660)
posix_fcntl_lock: WARNING: lock request at offset 2147483539, length 1
returned
[2002/09/21 00:01:25, 0] locking/posix.c:posix_fcntl_lock(662)
an Invalid argument error. This can happen when using 64 bit lock
offsets
[2002/09/21 00:01:25, 0] locking/posix.c:posix_fcntl_lock(663)
on 32 bit NFS mounted file systems.
[2002/09/21 00:01:25, 0] locking/posix.c:posix_fcntl_lock(660)
posix_fcntl_lock: WARNING: lock request at offset 2147483539, length 1
returned
[2002/09/21 00:01:25, 0] locking/posix.c:posix_fcntl_lock(662)
an Invalid argument error. This can happen when using 64 bit lock
offsets
[2002/09/21 00:01:25, 0] locking/posix.c:posix_fcntl_lock(663)
on 32 bit NFS mounted file systems.
[2002/09/21 00:01:25, 0] locking/posix.c:posix_fcntl_lock(660)
posix_fcntl_lock: WARNING: lock request at offset 2147483539, length 1
returned
[2002/09/21 00:01:25, 0] locking/posix.c:posix_fcntl_lock(662)
an Invalid argument error. This can happen when using 64 bit lock
offsets
[2002/09/21 00:01:25, 0] locking/posix.c:posix_fcntl_lock(663)
on 32 bit NFS mounted file systems.
[2002/09/21 00:02:03, 0] smbd/oplock.c:oplock_break(796)
oplock_break: receive_smb timed out after 30 seconds.
oplock_break failed for file Cluster/WesternScientific/Mit911a.xls (dev
= 9, inode = 1097925642, file_id = 56).
[2002/09/21 00:02:03, 0] smbd/oplock.c:oplock_break(868)
oplock_break: client failure in oplock break in file
Cluster/WesternScientific/Mit911a.xls
[2002/09/21 00:02:13, 0] locking/posix.c:posix_fcntl_lock(660)
posix_fcntl_lock: WARNING: lock request at offset 2147483539, length 1
returned
[2002/09/21 00:02:13, 0] locking/posix.c:posix_fcntl_lock(662)
an Invalid argument error. This can happen when using 64 bit lock
offsets
[2002/09/21 00:02:13, 0] locking/posix.c:posix_fcntl_lock(663)
on 32 bit NFS mounted file systems.
[2002/09/21 00:02:13, 0] locking/posix.c:posix_fcntl_lock(660)
posix_fcntl_lock: WARNING: lock request at offset 2147483539, length 1
returned
[2002/09/21 00:02:13, 0] locking/posix.c:posix_fcntl_lock(662)
an Invalid argument error. This can happen when using 64 bit lock
offsets
[2002/09/21 00:02:13, 0] locking/posix.c:posix_fcntl_lock(663)
on 32 bit NFS mounted file systems.
[2002/09/21 00:02:13, 0] locking/posix.c:posix_fcntl_lock(660)
posix_fcntl_lock: WARNING: lock request at offset 2147483539, length 1
returned
[2002/09/21 00:02:13, 0] locking/posix.c:posix_fcntl_lock(662)
an Invalid argument error. This can happen when using 64 bit lock
offsets
[2002/09/21 00:02:13, 0] locking/posix.c:posix_fcntl_lock(663)
on 32 bit NFS mounted file systems.
Also there are other things like:
[2002/09/21 00:21:02, 0] locking/posix.c:posix_fcntl_lock(660)
posix_fcntl_lock: WARNING: lock request at offset 2147483538, length 1
returned
[2002/09/21 00:21:02, 0] locking/posix.c:posix_fcntl_lock(662)
an Invalid argument error. This can happen when using 64 bit lock
offsets
[2002/09/21 00:21:02, 0] locking/posix.c:posix_fcntl_lock(663)
on 32 bit NFS mounted file systems.
[2002/09/21 00:57:30, 0] lib/util_sock.c:read_data(436)
read_data: read failure for 4. Error = No route to host
[2002/09/21 00:57:30, 1] smbd/service.c:close_cnum(690)
husainvm (172.16.65.128) closed connection to service husain
[2002/09/21 00:57:30, 1] smbd/service.c:close_cnum(690)
husainvm (172.16.65.128) closed connection to service husain
[2002/09/21 00:57:30, 1] smbd/service.c:close_cnum(690)
husainvm (172.16.65.128) closed connection to service 60GB
[2002/09/21 00:57:30, 1] smbd/service.c:close_cnum(690)
husainvm (172.16.65.128) closed connection to service husain
[2002/09/21 10:10:42, 1] smbd/service.c:make_connection(651)
husainvm (172.16.65.128) connect to service husain as user husain
(uid=45325, gid=101) (pid 5035)
[2002/09/21 10:15:49, 1] smbd/service.c:make_connection(651)
husainvm (172.16.65.128) connect to service 60GB as user husain
(uid=45325, gid=101) (pid 5035)
[2002/09/21 10:16:01, 1] smbd/service.c:make_connection(651)
husainvm (172.16.65.128) connect to service 60GB as user husain
(uid=45325, gid=101) (pid 5035)
[2002/09/21 10:28:36, 0] lib/util_sock.c:read_data(436)
The output of route is:
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use
Iface
172.16.65.0 * 255.255.255.0 U 0 0 0
vmnet1
192.168.78.0 * 255.255.255.0 U 0 0 0
vmnet8
18.98.0.0 * 255.255.0.0 U 0 0 0
eth0
127.0.0.0 * 255.0.0.0 U 0 0 0 lo
default RTR.xxx.xx 0.0.0.0 UG 0 0 0
eth0
the Win2k machine has this routing information (note that it has 2
virtual NIC's one connected to the outside world and one connected to the
internal network that is vmnet1 on the Linux box):
C:\>route print
==========================================================================Interface
List
0x1 ........................... MS TCP Loopback interface
0x2 ...00 50 56 e1 18 76 ...... AMD PCNET Family Ethernet Adapter
0x3 ...00 50 56 40 2e e6 ...... AMD PCNET Family Ethernet Adapter
====================================================================================================================================================Active
Routes:
Network Destination Netmask Gateway Interface
Metric
0.0.0.0 0.0.0.0 18.98.0.1 18.98.3.20
1
18.98.0.0 255.255.0.0 18.98.3.20 18.98.3.20
1
18.98.3.20 255.255.255.255 127.0.0.1 127.0.0.1
1
18.255.255.255 255.255.255.255 18.98.3.20 18.98.3.20
1
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1
1
172.16.65.0 255.255.255.0 172.16.65.128 172.16.65.128
1
172.16.65.128 255.255.255.255 127.0.0.1 127.0.0.1
1
172.16.255.255 255.255.255.255 172.16.65.128 172.16.65.128
1
224.0.0.0 224.0.0.0 18.98.3.20 18.98.3.20
1
224.0.0.0 224.0.0.0 172.16.65.128 172.16.65.128
1
255.255.255.255 255.255.255.255 172.16.65.128 172.16.65.128
1
Default Gateway: 18.98.0.1
==========================================================================Persistent
Routes:
None
Help!!!
Thanks,
Husain
Possibly Parallel Threads
Wisdom of the Ancients
