Bug 3683 - error when trying to launch setup.exe from a MS Office distributive from a Samba server
error when trying to launch setup.exe from a MS Office distributive from a Sa...
Status: REOPENED
Product: Samba 3.0
Classification: Unclassified
Component: File Services
3.0.24
x86 Windows XP
: P3 normal
: none
Assigned To: Samba Bugzilla Account
Samba QA Contact
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2006-04-14 06:35 UTC by drookie
Modified: 2007-02-13 08:23 UTC (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description drookie 2006-04-14 06:35:03 UTC
When I launch a setup.exe from a MS Office distributive residing on a Samba server, on my WinXP I see "Settings file <path> is missing or invalid. Please ensure this file exists and is accessible." File exists and is accessible by any programs like windows explorer, Far, etc.

On a SMB server I see in logs:

===Cut===
[2006/04/14 17:28:33, 0] locking/posix.c:posix_fcntl_lock(666)
  posix_fcntl_lock: WARNING: lock request at offset 208896, length 32768 returned
[2006/04/14 17:28:33, 0] locking/posix.c:posix_fcntl_lock(667)
  an Invalid argument error. This can happen when using 64 bit lock offsets
[2006/04/14 17:28:33, 0] locking/posix.c:posix_fcntl_lock(668)
  on 32 bit NFS mounted file systems.
===Cut===

Seup.exe resides on a ISO image, image is on local filesystem and is locally attached with mdconfig -a -t vnode -f <path> and then mounted to mounting points. Samba 2.x in the same environment(on the same machine) works fine. This is reproduceable, and I can supply logs with any wanted detalisation.
Comment 1 Volker Lendecke 2006-04-14 08:04:22 UTC
Does it also happen if you set 'posix locking = no'?

Volker
Comment 2 drookie 2006-04-14 09:11:02 UTC
Nope. Thanks, and sorry for bothering.
Comment 3 drookie 2006-04-14 09:16:52 UTC
(have read man smb.conf in 2.x and 3.x and now have a question)
Can be 'posix locking = no' used in production ? Its written in both mans that it shouldnt be tweaked normally.
Comment 4 Jeremy Allison 2006-04-14 10:33:39 UTC
It is only designed to be changed in situations like this where the POSIX locking isn't working correctly. I'd like to know more about the mounted filesystem where this fails - can you give me an output from mount please ?

Jeremy.
Comment 5 drookie 2006-04-16 23:12:51 UTC
# mount
[...]
/dev/md0 on /mnt/cdrom01 (cd9660, local, read-only)

smb.conf:
[global]
workgroup = SOFTLAB
netbios name = NS
server string = Samba 3.0.21a on FreeBSD 6.0-RELEASE
hosts allow = 192.168. 127. 172.16.
guest account = pcguest
map to guest = bad user
log file = /var/log/samba/log.%m
security = domain
password server = 192.168.3.6, 192.168.0.9
encrypt passwords = yes
socket options = TCP_NODELAY
dns proxy = no
local master = no
os level = 32
interfaces = vlan1 vlan5 lo0
bind interfaces only = yes
log level = 1
syslog = 4
deadtime = 15
wins server = 192.168.3.6
printcap name = cups
printing = CUPS
unix charset = KOI8-R
dos charset = 866

[cd-rom-01]
directory mask = 775
directory security mask = 000
comment = CD-ROM #1
path = /mnt/cdrom01
guest ok = yes
guest only = yes
browseable = yes
writeable = no
Comment 6 drookie 2007-02-13 08:23:08 UTC
Same behaviour on 3.0.24 (disabling 'posix locking' still helps).
Same behaviour with 3.0.24, even with 'posix locking = yes' and a udf-image mounted locally and redistributed via samba.