Scott, (cc Samba list) Quoting Scott Merrill <skippy@skippy.net>:> Federico, > I read with great interest your post to the Samba mailing list about Excel > files corrupting on a Samba share. > (http://lists.samba.org/pipermail/samba/2002-March/068091.html) > > I ran into a very similar situation, and came across your post while > scanning the mailing list archives looking for answers. > > My particular situation is a little more bizarre: > A user opens an Excel file (we're using Office 2000 on Win98SE). > Click "File", and select "Save As". > Save the file as itself. > > A dialog pops up announcing that the file was saved, but the workstation is > low on memory. > > Any attempt to open the recently saved file causes Excel to complain that > the data is not in a recognized format.Oh my. This doesn't sound good at all. Is this reproducible? Anything in the logs? My problems weren't as predictably reproducible, although it happened often. Perhaps the lack of user feedback was also a major factor in my inability to test the problem further than I was able to.> I'm currently running Samba 2.2.2 on an SGI Octane running IRIX 6.5.14m > with an XFS filesystem.Currently we're using Samba 2.2.3a, using the samba-2.2.3a-6 Debian packages on Linux with kernel 2.4.18-xfs and an XFS filesystem.> I'm intensely curious whether the "oplocks = no" and "nt acl support = no" > options have corrected your symptoms?"nt acl support = no" didn't seem to have much effect, but I left it in anyway since I don't need that feature. "oplocks = no" seems to have been the effective cure. We haven't had data corruption, since. Speed hasn't decreased significantly -- or at least not significant enough to be humanly noticed. Perhaps this is because the load is nowhere near enough to bring the server down to its knees even if everyone accessed all sorts of files heavily at the same time. But of course this has never happened so I'm going out on a limb here. It's my long way of saying "so far so good, but YMMV". :) --> Jijo -- Federico Sevilla III : <http://jijo.free.net.ph/> Network Administrator : The Leather Collection, Inc. GnuPG Key Fingerprint : 0x93B746BE
Dan Horth
2002-Apr-17 08:17 UTC
[Samba] Reliable Build (Was Re: Samba and Excel corruption)
Hi - I've been running a samba 2.2.1a server for some time now, with no evident problems regarding file corruption or other information loss. I'm in the process of moving samba to a different server - both running on Intel based hardware, Redhat 7.2 with all errata applied. I have been having some odd problems with profiles, printing, and printer driver setup / downloading and was considering upgrading to 2.2.3a in an attempt to remedy these and improve overall reliability. I was wondering if anyone could share any horror or success stories with either of these builds - or even suggest whichmight be the best build to use to service a small number of mixed clients - Win98 and NT4 with one 2000 and oneXP laptop. I'd rather server stability and reliability to "sysadmin conveniences", while maintaining best interoperability with the variety of clients. I'm planning on building and testing the SAMBA_2_2 branch from samba CVS tomorrow - but cannot afford to invest thetimeright now if there are known reliability / data integrity problems. Any advice would be appreciated. Even short references to specific problems (ie word 2000 file corruption with 2.2.3) if they're known issues will help enormously in my research and decision. I'd be glad to summarise replies to individuals or the list if desired. Thanks in advance, Dan. Re:>I read with great interest your post to the Samba mailing list about Excel >files corrupting on a Samba share.<snip>>Any attempt to open the recently saved file causes Excel to complain that >the data is not in a recognized format.and>I am running Samba 2.2.3 on Red Hat 7.2 with Win XP work stations. > >Everything is working fine except for when I try to save a file from Word 2000 >to a share on Samba. The file saves OK but will not re-open, I get the error