I am having a bit of a problem running samba 2.2.1a on Tru64 5.1a.
Until very recently I have been running samba 2.0.7 without any
problems. I don't so much expect this list to provide me with a
solution (though it would be great if somebody knows how to fix the
problem...), rather I would like to find out if anybody else using
samba 2.2.1a is having similar difficulties.
Below is the message I sent to the samba mailing list describing the
problem. I will summarize any useful responses I receive from this
list and the samba list.
To: samba_at_lists.samba.org
Subject: File corruption with 2.2.1a, Tru64 5.1, and Excel under Win98
Date: Mon, 30 Jul 2001 16:47:30 -0600
From: Jeff Lessem <lessem_at_ibg.colorado.edu>
I recently upgraded samba on my Alpha running Tru64 5.1 from 2.0.7 to
2.2.0a. Everything seemed to work fine, but I am getting a strange
problem with Excel from Office 2000 and Windows 98. This problem only
seems to occur with Windows 98, as I couldn't reproduce it with
Windows 2000[1].
Opening an existing Excel worksheet stored on a share from the server
is fine. Simply clicking on the floppy disk save icon and then
closing Excel will prevent the file from being opened again. Excel
fails to open the file with a dialogue box saying "Unable to open
file" (The file can be opened with wordpad, though it just gibberish).
The .xls file then appears to be permanently corrupted, as copying it
to the desktop does not allow it to be opened. The .xls file saved
(with no changes) is the same size as the original file, but it does
differ from the original. I do not know enough about .xls files to
know if the changes are unusual.
Falling smbd back to smbd.old makes the problem go away (a broken file
is still broken, but a good file won't be broken by opening and saving
it). I built samba with Compaq's cc -fast. I tried again with -O0,
but that had no effect on the problem. I also tried building samba on
a Tru64 4.0d machine (with cc) and ran the resulting smbd binary under
5.1, but the problem persists.
I am not sure which files would be useful for debugging information
(smb.conf, config.cache, log.smb, etc.). I turned debug level up, but
nothing out of the ordinary seemed to be reported. Of course Excel
gives no sort of useful information. Just let me know what debugging
information would be useful in tracking down this problem and I will
provide it.
[1] Earlier this morning a user reported that Word from Office 2000
under Windows 2000 crashed while saving a file, and then that file
couldn't be opened again. The temporary file created by Word (and
left behind) could be opened and contained most of the changes which
had been made. I don't necessarily want to lump this in with the
problem I report above, because in this case Word crashed, while Excel
reports that nothing is wrong.
--
Thanks,
Jeff Lessem.
Received on Tue Jul 31 2001 - 00:11:57 NZST