[Samba] More files randomly corrupted

david de leeuw david at bgumail.bgu.ac.il
Wed Sep 17 07:39:58 GMT 2003


Hi Steve,

We had this on two occasions recently. Caused by different causes each time.
Once with the version 3 beta 3, once with version 3 release candidate 2 and
with rc 3.
Now all is fine with 3 rc 4.
The first thing to check out if there are any "panic" messages in the logs.
We had loads of panics, apparently caused by problems in joining the domain,
the kerberos set up and multicharacter (non-English) character filenames.
When the "panic" strikes the session is ended, and the user might see a
corrupt file.
A new session is established automatically. If the file is saved, the file
on the server is corrupted as well !

The morale: check out "panics" in logs.

David de Leeuw
Ben Gurion University of the Negev
----- Original Message ----- 
From: "Steve Jr Ramage" <sjr at sjrx.net>
To: <samba at lists.samba.org>; <samba-technical at lists.samba.org>
Sent: Wednesday, September 17, 2003 4:04 AM
Subject: [Samba] More files randomly corrupted


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Still having that problem with samba seemingly corrupting files, it seems to
be the same files that are corrupted again and again, yet they are corrupted
differently and sometimes not. I ran my md5 summer against one file
ch02.pdf, and it almost contineously corrupts, I checked in a hex editor and
there are some differences. Yet the problem is that its not read the same
way each time. The md5 changes and oddly enough this seems to affect some
files more than other. Ironically ch02.pdf is eBook on Samba, ch01, and ch03
almost never seem corrupted I've moved both of the files to see if directory
depth has anything to do. And it doesn't I also checked another machine, now
the other machine running the same version of samba (Samba 2.2.3a [Debian
Version]), yet diff versions of debian (stable vs. testing). I can't figure
it out, I don't know whats causing this or where to start really. To make it
worse someone told me there isn't anything in the samba code to cause this.

Finally all the files that seem to be corrupted when being read, seem to be
intact on the file system they are stored on.



Steve Jr Ramage
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (MingW32)

iD8DBQE/Z8E/EK+EAP2ExcQRAqOVAKDIrF0eQ49ncWFleew/pHUWFck2jACfcmAg
Q1T4tycY/pCCRfHadifb4pg=
=rotn
-----END PGP SIGNATURE-----


-- 
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba




More information about the samba mailing list