On Thu, 2006-01-05 at 14:48 -0500, Justin Mazzola Paluska wrote: > On Tue, Dec 20, 2005 at 08:08:24AM -0800, Jeremy Allison wrote: > > Ok, what you need is to create files locally on the windows client > > of 512 bytes, 1024 bytes etc. and then just copy them onto the > > Samba drive. Check what the smallest size is that the first file becomes > > corrupted. That will show the simplest problem that reproduces the > > issue. At *that* point then send in logs etc. Without an *exact* > > method of reproducing this with detailed information on what is > > going wrong (ie. the last 20 bytes of a 512 byte file get corrupted, > > but a 256 byte file is fine - here is the comparitive copy) it will > > be a massive investment of time to track this down, that we currently > > don't have. You're going to have to do more work on this I'm afraid. > > OK, I made a bunch of files consisting of the string > "123456789abcdef\n" where \n is the UNIX newline (ASCII 0xA) and > performed the binary search. Files 64KB (=65536 bytes) and higher are > corrupted and files under 64KB are fine.
Have you looked into tools such as fsx and fstest to determine this isn't a filesystem failure? http://www.freebsd.org/cgi/cvsweb.cgi/src/tools/regression/fsx/ http://samba.org/ftp/unpacked/junkcode/fstest.c Andrew Bartlett -- Andrew Bartlett http://samba.org/~abartlet/ Authentication Developer, Samba Team http://samba.org Student Network Administrator, Hawker College http://hawkerc.net
signature.asc
Description: This is a digitally signed message part
-- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba