Process no longer exists (still after much hassle)

Jeremy Allison jra at samba.org
Wed Jan 16 10:46:48 GMT 2002


On Wed, Jan 16, 2002 at 12:11:03PM -0500, Adam Tauno Williams wrote:
> Hardware: IBM Netfinity 5500, Dual PIII, 512Mb, IPS RAID
> 
> Network Information: The PDC is a Samba-2.2.1a box on RH 7.0 attached to the
> same switch.  Clients are Win95, Win98, WinNTsp5, and Win2000pro.
> 
> Initial configuration: RedHat 7.0 and Samba 2.2.1a, stable as a rock
> 
> Upgraded to RH7.2+SGI/XFS (need ACL support),  with the same Samba 2.2.1a. 
> Lotus 1-2-3 users reporting "File is corrupt" messages when trying to save,  but
> otherwise everything seems to work.  
> 
> I tried turning off oplocks, but no luck.  I turned them back on.
> 
> In order to try and fix that I though I might just recompile,  but the Samba's
> won't compile on RH7.2 due to some fsstat define thing.  
> 
> So I try going back to an older Samba, 2.0.7.  I remove the 2.2.1a RPM and
> install the 2.0.7 RPMS,  these install happily and start.
> 
> The Lotus 1-2-3 user no longer recieve any errors,  but after a while M$-Office
> users are unable to save *their* files!
> 
> I tried turning off oplocks, but no luck.  I turned them back on.
> 
> So I check for error messages, and check cables, surf the net, et al.  And I
> find my error messages (below) referenced but no fix suggested.  
> 
> So I think, maybe it isn't really Samba, but a system problem.  I upgrade to the
> very latest GLIBC available from 2.2.4-19.3 and the kernel 2.4.14 from
> kernel.org with the XFS 1.0.2 patch applied. 
> 
> But I still have the exact same problem.  Any assistance would be greatly
> appreciated (I've been using Samba since 1.9.15 and never had a problem anywhere
> near this bad).

This is a bug that was being worked on, a fix was applied for 2.2.2, further
scalability fixes have been added for 2.2.3 (due soon). My suggestion is to
try 2.2.2, and upgrade to 2.2.3 when it is released.

Regards,

	Jeremy.




More information about the samba mailing list