similar to: Re: samba oplocks problem

Wolfgang, (cc Linux XFS list) (cc Samba list) Quoting wolfgang.glas@ev-i.at: > I just found you message in the samba mailing list archives and foiund > out, that we have a very similar problem. We are using samba-2.2.1a on a > kerenl-2.4.16 and we use reiserfs. > We also experience data corruption with messages like: > > [2002/03/14 15:15:26, 0] >

Hi everyone, Just today one of our users informed me that a file she was working on in Microsoft Excel 97 got corrupted. She was working on the file directly on our server, which is running Samba 2.2.3a compiled using gcc-3.0.4 on Linux kernel 2.4.17-xfs and XFS-based filesystems. I checked the Samba logs for her machine and found the following in a search for the filename of the Excel file she

Hi everyone, Our system is a Debian GNU/Linux box running Linux kernel 2.4.17-xfs and Samba 2.2.3 (from the 2.2.3-5 package from Sid), built using gcc-3.0.3. With Samba 2.2.2 we hit certain tdb errors where make_connection would reject connections arbitrarily. Supposedly this was fixed using 2.2.3 so we upgraded right away (thankfully we do only have Windows 95, 98 and ME clients so we

Suddenly, today, my wife's Windows 95 machine can't print to the network printer on my Linux machine. It complains that "there was an error printing to \\posh\lp ... There was a problem printing to the port." The error 1st occurred (coincidentally?) after I had upgraded the kernel from 2.4.18 to 2.4.19. But rebooting to 2.4.18 has made no difference. We're running smbd

too. However, when I mount the share via smbfs (on a Linux box, of course), the same file is 2.0T as reported by du (ie: du -csh), 18446744072754680087 bytes as reported by ls, but is only 3340095767 bytes as reported by stat. Further comparison of stat results of the same file via smbfs and directly are intriguing. directly (ie: on the server): Size: 3340095767 Blocks: 6523640 IO Block: 4096

Hi there everyone, I recently upgraded to 2.0.6 from 2.0.5a in a hope to improve data integrity (I was having oplock_break problems that would affect the integrity of a lot of Excel files). So far so good with the oplock_breaks (even with oplocks reenabled). :-) However, I've started having problems with the clients' Windows profiles not being placed in my defined logon path.

Hi there everyone! I'm using Samba 2.0.5a-19990721 on a RedHat 6.0 machine with Linux kernel 2.2.12. My system generally works fine, however recently I've had some complaints about some files being corrupted. The latest and best-handled to enable a debugging happened at around the same time. Both clients were using Windows95 OSR2 machines with Excel 97 SP-2. Two users reported the problem

Hi Federico, many thanks to you. This patch helped me too. Do you know the intention of the original changes by the samba team in ipc.c. I don't think, it is a good idea to store all profiles in an separate directory and the user registry in the home path. Thanks again Rudolf Rudolf Kollien email: Rudolf.Kollien@medas.de Rudolf.Kollien@kollien.de

Hi there everyone! One of the users complained to me that yesterday, he suddenly couldn't access the network. He was online the whole day, then suddenly at around 6:45pm he couldn't write. A restart of his workstation rendered him completely disconnected from the Samba domain. Server is running Samba 2.0.6 on a RedHat 6.0 machine with Linux kernel 2.2.13. Client is running Windows95 OSR2

Hi there everyone, Again another slight thing I noticed since I upgraded to Samba 2.0.6 from 2.0.5a. I'm using RedHat Linux on a Celeron 400 with kernel 2.2.13. My socket options in smb.conf is set to "TCP_NODELAY IPTOS_LOWDELAY SO_KEEPALIVE SO_SNDBUF=8192 SO_RCVBUF=8192". However I've started getting the following everytime I SIGHUP to reload the configs and stop-start:

hello, until last week I had 2.2.1a in place, which, except some fox (dos) share which needed 'veto oplocks files', worked ok; upgraded to 2.2.3a with the same smb.conf (details below) and suddenly I started having oplocks problems (not on the dos share, that one is ok) with almost every other share (those hold windows files: programs, *doc, *xls): [2002/02/19 12:31:28, 0]

Can any one help me ? This has been bugging me for ages. I have been using different versions of samba for a while on different versions of Redhat (7.0, 7.2, 7.3). I regularly get erratic freezing (for about a minute) whenever I right click on files. This has happened on different computers on different sites on different networks, so I assume it's quite consistent This is what I get when

Hello there. I'm having a few problems using samba 2.2.3a and sharing a paradox database. On the whole everything works fine but (there's always a but), every now and again. a machine's shares will close causing the database to crash (sometimes only that machine) - the other networked machine recover after a few error messages. I guess the easy answer would be to disable oplocks

In my smb.conf file, I've got the following section: [homes] comment = Home Directories valid users = %S guest ok = no read only = No create mask = 0640 directory mask = 0750 browseable = No veto oplock files = /*.mdb/*.MDB/*.pst/*.PST/ And yet, in the syslog, I'm still getting these... Mar 10 10:22:34 riffraff

Hi all, I use samba 2.2.2 on AIX 4.3.2 (1500 NT4 sp6a / w2k sp2 workstation). since i had updated from 2.0.7 to 2.2.2 the CPU load will very fast go to 100% an d teh memory use of a smbd process will grow up to 100 MB. In teh log-files are many errors like that: PANIC: open_mode_check: Existant process 22700 left active oplock smbd/open.c:open_mode_check(555) open_mode_check: exlusive oplock

Hello list! I've seen the threads in this months archives on oplock issues, so I hope I am not hitting a sore spot by bringing it up again. The reason I am beating on this is that I've got a testable, repeatable issue with Win2K terminal server (SP2) running CorelDRAW 10 (patched to current) against a Debian Woody box running Samba 2.2.3a-6 for Debian. Since I can repeatedly test the

Hi! I keep getting errors like these: oplock_break failed for file Word/einaikoon/v-Locator/IBB-Beantragung/0_Antrag_AZK.doc (dev = 301, inode = 2469218, file_id = 7). [2003/07/31 15:43:22, 0] smbd/oplock.c:oplock_break(843) oplock_break: client failure in break - shutting down this smbd. [2003/07/31 15:47:12, 0] smbd/oplock.c:oplock_break(758) oplock_break: receive_smb error (Success)

Below are a number of errors that appeared in a log file today. I am running Samba v2.2.5 on a Red Hat Linux v7.3 system. The client experiencing/causing the errors below is a WinXP(SP1) machine. The log entries below pertain to 2 errors, the first in handling file "6.zip" and the second in attempting to run file "DiskeeperWks413zssi.exe". I didn't see the first

I've used oplocks = no for a long time now, because of the famous "oplock_break" error, but I decided to give 2.0.7 a try. I still get "oplock break" errors as before, but this time I got a new error too: [2000/05/02 10:04:52, 0] smbd/oplock.c:oplock_break(976) oplock_break: receive_smb timed out after 30 seconds. oplock_break failed for file XXXXX/xxxxxx/mailbox.pst

Since switching from Samba 2.2.3a-6 on Debian stable to 3.0.2a packages from the samba.org server (system is Debian stable too) we've had extreme problems with Office documents. Samba acts as a PDC and the user log onto it. The LDAP Authentication works great. Our clients are all Windows 2000 and Office 2000. When opening documents word (excel) sometimes just hangs (for 30 seconds until