I believe that I've found a bug on Samba 2.2.3a. Sure, there is the 2.2.5 version out there, but reading the changelog I couldn't find something that looked like what I've found. Problem is: Some files (very few of them, about 0,5%) are created, with 2 another copies. The file witch would be the real one is perfect. And we got "for free" 2 corrupted copies of it, with the name mangled. So, say we copy the file "testfile.txt". We should end with just one file, but what we got is something like testfile.txt -> This one is perfect tes~1.txt -> This one is useless (about 1 k in size) tes2~1.txt -> This one is useless too. I couldn't found what makes this. What I found out is: 1) If a file is affected, is of no use to change its name - neither its extension. 2) If a file is NOT affected, is of no use to change its name - neither its extension 3) If we open an affected file (say a bmp) and save it with the same name, as a bmp too, the problem is gone. Looks like it has some to do with byte order, or something eles that gets changed with a rewrite of its contents. 4) Size does not matter. I have found it with 400K files, html pages and have copied flawleesy an Oracle zip file, of 900 Mb and long filemane - and this monster went trough it perfectly. My systems are: (both affected) Conectiva 8 Samba 2.2.3a Kernel 2.4.18 Both are up to date. Checked the vendor site to updates just 3 hours ago. The hardware: 1) K6 2 350 with: 64 Mb RAM 6 Gb HD Mainboard PCChips 598 (Sis Chipset) Kernel standart, the one which came with the Distro. 2) Athlon XP 1900 512 Mb DDR 266 RAM 2 HD 80 GB each, using software RAID 1 Mainboard ABIT, KX7333R Kernel recompiled, to athlon and + than 1 Gb of RAM (second memory is on the way) If you want, just ask me and I will send 2 or 3 files affected. If this is an already found bug, sorry for the inconvenience. Keep up with this excelent work of yours Best regards Marcelo Paternot Rodrigues paternot@sanap.com.br
Marcelo Paternot Rodrigues wrote:> > I believe that I've found a bug on Samba 2.2.3a. Sure, there is the 2.2.5 > version out there, but reading the changelog I couldn't find something that > looked like what I've found.Changelogs certainly don't incidate all changes, and certainly don't convey the kind of detail you would require for that kind of assertion. We mainly list changes that we *expect* to be user-visible. That said, you have a *very* interesting little problem here...> Problem is: > > Some files (very few of them, about 0,5%) are created, with 2 another copies. > The file witch would be the real one is perfect. And we got "for free" 2 > corrupted copies of it, with the name mangled. > So, say we copy the file "testfile.txt". We should end with just one file, but > what we got is something like > > testfile.txt -> This one is perfect > tes~1.txt -> This one is useless (about 1 k in size) > tes2~1.txt -> This one is useless too.Mangling is a mess in Samba 2.2, particularly < 2.2.5. It would be interesting to see if the new code in 2.2.5 (activated by 'mangling method = hash2' in your smb.conf) helps. Andrew Bartlett -- Andrew Bartlett abartlet@pcug.org.au Manager, Authentication Subsystems, Samba Team abartlet@samba.org Student Network Administrator, Hawker College abartlet@hawkerc.net http://samba.org http://build.samba.org http://hawkerc.net
> -----Original Message----- > From: Andrew Bartlett [mailto:abartlet@samba.org] > Sent: Wednesday, August 14, 2002 10:21 AM > To: Marcelo Paternot Rodrigues > Cc: samba@samba.org > Subject: Re: [Samba] Possibly a bug > > > Marcelo Paternot Rodrigues wrote: > > > > I believe that I've found a bug on Samba 2.2.3a. Sure, > there is the 2.2.5 > > version out there, but reading the changelog I couldn't > find something that > > looked like what I've found. > > Changelogs certainly don't incidate all changes, and certainly don't > convey the kind of detail you would require for that kind of > assertion. > We mainly list changes that we *expect* to be user-visible. > > That said, you have a *very* interesting little problem here... > > > Problem is: > > > > Some files (very few of them, about 0,5%) are created, with > 2 another copies. > > The file witch would be the real one is perfect. And we got > "for free" 2 > > corrupted copies of it, with the name mangled. > > So, say we copy the file "testfile.txt". We should end with > just one file, but > > what we got is something like > > > > testfile.txt -> This one is perfect > > tes~1.txt -> This one is useless (about 1 k in size) > > tes2~1.txt -> This one is useless too. > > Mangling is a mess in Samba 2.2, particularly < 2.2.5. It would be > interesting to see if the new code in 2.2.5 (activated by 'mangling > method = hash2' in your smb.conf) helps.I would guess that this actually caused by the infamous ADS bug. Let me guess Marcelo, this usually happens on picture files right ? N. -- Nir Soffer -=- Software Engineer, Exanet Inc. -=- "Father, why are all the children weeping? / They are merely crying son O, are they merely crying, father? / Yes, true weeping is yet to come" -- Nick Cave and the Bad Seeds, The Weeping Song
> -----Original Message----- > From: Andrew Bartlett [mailto:abartlet@samba.org] > Sent: Wednesday, August 14, 2002 3:27 PM > To: Nir Soffer > Cc: Andrew Bartlett; Marcelo Paternot Rodrigues; samba@samba.org > Subject: Re: [Samba] Possibly a bug > > > Nir Soffer wrote: > > > > > > > > > -----Original Message----- > > > From: Andrew Bartlett [mailto:abartlet@samba.org] > > > Sent: Wednesday, August 14, 2002 10:21 AM > > > To: Marcelo Paternot Rodrigues > > > Cc: samba@samba.org > > > Subject: Re: [Samba] Possibly a bug > > > > > > > > > Marcelo Paternot Rodrigues wrote: > > > > > So, say we copy the file "testfile.txt". We should end with > > > just one file, but > > > > what we got is something like > > > > > > > > testfile.txt -> This one is perfect > > > > tes~1.txt -> This one is useless (about 1 k in size) > > > > tes2~1.txt -> This one is useless too. > > > > > > Mangling is a mess in Samba 2.2, particularly < 2.2.5. > It would be > > > interesting to see if the new code in 2.2.5 (activated by > 'mangling > > > method = hash2' in your smb.conf) helps. > > > > I would guess that this actually caused by the infamous ADS bug. > > infamous? You might want to describe it a bit more, so I > know what you > are talking about... >2.2.3a didn't handle ADSs very well, so you would get, when copying a JPG file with ADSs associated to it, 3 files when copying it to a Samba share. (ADSs created by some odd media microsoft thingy) The 2 extra files would contain what would seem to the ordinary user like crap, since it's just metadata, they would also have large filenames, which explains the mangling. The first file would remain intact. 2.2.4 doesn't show the same behaviour. I think it was you who, when a coworker of me asked the same question, answered that, when we asked the same question a few monthes ago. Or was it Jerry? Nir. -- Nir Soffer -=- Software Engineer, Exanet Inc. -=- "Father, why are all the children weeping? / They are merely crying son O, are they merely crying, father? / Yes, true weeping is yet to come" -- Nick Cave and the Bad Seeds, The Weeping Song