Hi, the home directories of our users are NFS-mounted from a NetApp filer to our samba server. Everthing was fine until the users installed the service pack 3 for Windows XP on the client machines. Suddenly it was impossible to write MS Office files on the samba share. Word or Excel documents could only be opened in read-only mode. After de-installing SP3 everything worked well again. I found out that setting the samba option "posix locking = No" resolves the problem. The manual page of smb.conf says: "You should never need to disable this parameter." So I think this is only a temporary solution. Microsoft must have changed something regarding the locking mechanism inside the service pack. Any ideas? Our samba environment: Red Hat Enterprise Linux Server release 5.2 (Tikanga) Kernel 2.6.18-53.1.4.el5 Samba 3.0.30 Regards, Dirk Kastens
Hi, Im running XP SP3 here on samba 2.0.24 and 2.0.28 and no problems here. Louis>-----Oorspronkelijk bericht----- >Van: samba-bounces+belle=bazuin.nl@lists.samba.org >[mailto:samba-bounces+belle=bazuin.nl@lists.samba.org] Namens >Dirk Kastens >Verzonden: vrijdag 6 juni 2008 13:43 >Aan: samba@lists.samba.org >Onderwerp: [Samba] XP SP3 and posix locking > >Hi, > >the home directories of our users are NFS-mounted from a >NetApp filer to >our samba server. Everthing was fine until the users installed the >service pack 3 for Windows XP on the client machines. Suddenly it was >impossible to write MS Office files on the samba share. Word or Excel >documents could only be opened in read-only mode. After de-installing >SP3 everything worked well again. >I found out that setting the samba option "posix locking = No" >resolves >the problem. The manual page of smb.conf says: "You should >never need to >disable this parameter." So I think this is only a temporary solution. >Microsoft must have changed something regarding the locking mechanism >inside the service pack. >Any ideas? > >Our samba environment: >Red Hat Enterprise Linux Server release 5.2 (Tikanga) >Kernel 2.6.18-53.1.4.el5 >Samba 3.0.30 > >Regards, > >Dirk Kastens >-- >To unsubscribe from this list go to the following URL and read the >instructions: https://lists.samba.org/mailman/listinfo/samba >
On Fri, Jun 06, 2008 at 01:42:50PM +0200, Dirk Kastens wrote:> the home directories of our users are NFS-mounted from a NetApp filer to > our samba server. Everthing was fine until the users installed the > service pack 3 for Windows XP on the client machines. Suddenly it was > impossible to write MS Office files on the samba share. Word or Excel > documents could only be opened in read-only mode. After de-installing > SP3 everything worked well again. > I found out that setting the samba option "posix locking = No" resolves > the problem. The manual page of smb.conf says: "You should never need to > disable this parameter." So I think this is only a temporary solution. > Microsoft must have changed something regarding the locking mechanism > inside the service pack. > Any ideas?Well, re-export of NFS-imported directories is not recommended and one of the exceptions to "you should never..." :-) If you have NetApp installed, why re-export via Samba? License issues? Volker -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available Url : http://lists.samba.org/archive/samba/attachments/20080606/8ad85681/attachment.bin
Hi, L.P.H. van Belle wrote:> Hi, > > Im running XP SP3 here on samba 2.0.24 and 2.0.28 and no problems here.It works with local filesystems. I does not work with NFS-mounted filesystem. Regards, Dirk
i've had a similar problem for weeks/months now with microsoft word 2003 saying files are read-only, even when the file permissions are 777. i was google searching which said the problem is due to windows desktop search. i uninstalled that but that didn't completely fix it. i'll try posix locking = no Dirk Kastens wrote:> Hi, > > the home directories of our users are NFS-mounted from a NetApp filer > to our samba server. Everthing was fine until the users installed the > service pack 3 for Windows XP on the client machines. Suddenly it was > impossible to write MS Office files on the samba share. Word or Excel > documents could only be opened in read-only mode. After de-installing > SP3 everything worked well again. > I found out that setting the samba option "posix locking = No" > resolves the problem. The manual page of smb.conf says: "You should > never need to disable this parameter." So I think this is only a > temporary solution. Microsoft must have changed something regarding > the locking mechanism inside the service pack. > Any ideas? > > Our samba environment: > Red Hat Enterprise Linux Server release 5.2 (Tikanga) > Kernel 2.6.18-53.1.4.el5 > Samba 3.0.30 > > Regards, > > Dirk Kastens
Hi, Am Freitag, den 06.06.2008, 15:08 +0200 schrieb Dirk Kastens:> Hi, > > L.P.H. van Belle wrote: > > Hi, > > > > Im running XP SP3 here on samba 2.0.24 and 2.0.28 and no problems here.2.0.xx I hope this is a typo and 3.0.xx is meant?> It works with local filesystems. I does not work with NFS-mounted > filesystem. > > Regards, > DirkI need to agree (to a certain degree) to L.P.H. van Belles mail. I tested it with a current WinXP SP3 and all other security Patches with a fairly old Samba (3.0.14a, Debian sarge, oldstable, will be upgraded in the maybe not so near future though *g*) with some via samba shared nfs exports. But here are symbolic links used to link to the files on the nfs export: /mnt/nfs #the mounted nfs export /pub/samba #the samba share /pub/samba/old_data #a symbolic link /mnt/nfs/data #the target of the link above So after all this may be the difference AND a workaround for Dirks problem. I did check the samba configuration, posix locking is not set, default is used (maybe the default changed?). regards Michael
Hi,> So after all this may be the difference AND a workaround for Dirks > problem. I did check the samba configuration, posix locking is not set, > default is used (maybe the default changed?).The default is "posix locking = Yes". We also use symbolic links. The samba server mounts the filesystem /vol/student from the NetApp on /mnt/fs4/student. We created a symbolic link from /mnt/fs4/student to /home/student and we created a home-share with "path = %H". This works for years and it still works with XP SP3. You can create files with Wordpad or Notepad or OpenOffice, for example. Only MS Office stopped working after installing SP3. Vista and other OSes still work. -- Regards, Dirk -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 6312 bytes Desc: S/MIME Cryptographic Signature Url : http://lists.samba.org/archive/samba/attachments/20080609/d2cb2e42/smime.bin
Hi,
yeah, meant 3.0.x, sorry about the.
this is how my filesystem is setup.
( On server1 )
sambaserver = /home/samba/datadir/ ( PDC + ACL + ea ) Kernel 2.6.18-4 (
debian )
Datadir is shared, this is my global data folder for users.
Sambausers /users/ The users personal folder
nfslinked /home/users/userfolder/"symlinked folder to a
XXXX1/subfolder" ( this folder comes from sco unix 5.0.7 NFS V2 )
nfsmount /home/nfsmount/XXXXX1 nfs mounted folder, shared in
sambaserver als XXXX1 ( i have 3 of these folders ) ( chmod 777 )
nfslinked2 /home/nfsmount/XXXXX2 nfsmounted folder on debian etch,
linked in "Datadir" as temp folder "chmod 777" is used.
( UNIX )
mounted the user home dir from debian in /u/
dont ask why but im have lots of cross server scripts running here.
And still expanding..
Also.
i created 1 "nfs user" on the debian server, i gave these the same
UID/GID
as on my unix server
saved problems with rights.
in samba i forced these users so these are always the unix user.
this is not done in the nfslinked folders. these are users personal folders.
on my WXP sp3 im running Mcafee 8.5 Enterprise Patch 5.
Are you aware it could also be a problem in the virusscanner your using?
Hope this info helps a bit.
here a part of my settings.
map hidden = no
map system = no
map archive = no
store dos attributes = yes
ea support = yes
dos charset = 850
preserve case = yes
short preserve case = yes
case sensitive = auto
directory mask = 0755
hide dot files = yes
hide unreadable = yes
hide files = /RECYCLER/desktop.ini/Desktop.ini/Thumbs.db/
veto files = /*.eml/*.nws/*.{*}/
veto oplock files = /*.doc/*.xls/*.mdb/
dont descend = /proc,/dev,/etc,/lib,/lost+found,/initrd
create mask = 0644
kernel oplocks = Yes
lock spin time = 200
oplock break wait time = 0
lock directory block size = 1024
veto oplock files = /*.doc/*.xls/*.mdb/
blocking locks = Yes
fake oplocks = No
locking = Yes
oplocks = Yes
level2 oplocks = Yes
oplock contention limit = 2
posix locking = Yes
strict locking = Auto
Louis
>-----Oorspronkelijk bericht-----
>Van: samba-bounces+belle=bazuin.nl@lists.samba.org
>[mailto:samba-bounces+belle=bazuin.nl@lists.samba.org] Namens
>Michael Schmitt
>Verzonden: zaterdag 7 juni 2008 22:47
>Aan: samba@lists.samba.org
>Onderwerp: Re: [Samba] XP SP3 and posix locking
>
>Hi,
>
>Am Freitag, den 06.06.2008, 15:08 +0200 schrieb Dirk Kastens:
>> Hi,
>>
>> L.P.H. van Belle wrote:
>> > Hi,
>> >
>> > Im running XP SP3 here on samba 2.0.24 and 2.0.28 and no
>problems here.
>
>2.0.xx I hope this is a typo and 3.0.xx is meant?
>
>> It works with local filesystems. I does not work with NFS-mounted
>> filesystem.
>>
>> Regards,
>> Dirk
>
>I need to agree (to a certain degree) to L.P.H. van Belles mail. I
>tested it with a current WinXP SP3 and all other security
>Patches with a
>fairly old Samba (3.0.14a, Debian sarge, oldstable, will be upgraded in
>the maybe not so near future though *g*) with some via samba shared nfs
>exports. But here are symbolic links used to link to the files on the
>nfs export:
>
>/mnt/nfs #the mounted nfs export
>/pub/samba #the samba share
>/pub/samba/old_data #a symbolic link
>/mnt/nfs/data #the target of the link above
>
>So after all this may be the difference AND a workaround for Dirks
>problem. I did check the samba configuration, posix locking is not set,
>default is used (maybe the default changed?).
>
>regards
>Michael
>
>--
>To unsubscribe from this list go to the following URL and read the
>instructions: https://lists.samba.org/mailman/listinfo/samba
>