vince@rti.com (Vince Chen) write:>We upgraded from samba 1.9.17 to 1.9.18 (now running p7) in hopes of >solving file-corruption problems when large files are copied to >NT from our IRIX 6.2 samba server. > >Has anyone see any file corruption?This won't solve your problem, but I just ran some tests copying a large file from NT to FreeBSD2.2.6 and back, w/o any sign of corruption. Just wanted to report these measurements: Copying a 45Mb Exchange InBox file (all my email, incl Samba digest) from NT to a Samba share, 1.9.18p3, both PC's a P100Mhz, using an crossover cable connecting two 10mbps NE2000 NIC's, copying with dos session 'copy' (desktop drag and drop is broken and I don't feel like fixing any more of billy's stuff). -took approx 1 min 10 secs, used 60% of NT CPU (NT doing nothing else), but 'top' on FreeBSD reports smbd using only 12% max CPU, and 55% network utilization reported by perfmon -ran 'comp' on NT dos session, files compared ok. -copy file back from FreeBSD, again took 1 min 10 secs, 60% NT CPU, 55% network, and 'top' reports smbd %cpu climbing steadily to a max of 35% cpu. -Startup Inbox and open mail file, compacted, open some of the first messages, all ok, no sign of corrpution. The set of 4 FreeBSD cd's comes with Samba as a package and sure seems like a bargain. Chuck B.S.E.E. McSE cswiger@norfolk.infi.net
Chuck, (ALL), THanks for doing the tests. There's another pattern that we've noticed: All corruption happens when extracting an archive (.ZIP, .TAR) or directly running self-extracting archives (.EXE). One of the first times we ran into this is w/ the NT 4.0 Service Packe 3 self-extracting archive. The file lives on Samba and we run it from the NT machines. We also have other self-extracting installers that have the same problem. Once the problem occurs, copying that same file also ends up in corrupted files. The problem is, this is sporadic. With freshly booted Samba and NT machines, it doesn't happen. It creeps in sometime later. -vince
Hello, I use samba on SCO OpenServer 5.0.5 (rs505a, oss497c, oss600a) as a NT-Domainmember. With 2.0.3 everything was fine for months. After upgrading to 2.0.5a we encountered filesystemcorruption so I downgraded back to 2.0.3. 2 weeks ago I reinstalled OpenServer and Samba. 2.0.3 and 2.0.5a did not work at all. Logfile says "ERROR: root did not create the semaphore" and "ERROR: Failed to initialise share modes!". 2.0.6 work, but we encounter file corruption. Opening the same file with MS-Word sometimes work fine, sometimes gives error messages. In the logfile I find: locking/locking_shm.c:shm_get_share_modes(213) get_share_modes: process 26765 no longer exists locking/locking_shm.c:shm_get_share_modes(241) get_share_modes: file with dev 168 inode 183144 empty I have exported the filesystem through NFS and mounted it to a linuxbox and there Samba 2.0.5a (and NFS) works great. No problems accessing the same file. -- Tommi M?kitalo Dr. Eckhardt + Partner GmbH t.maekitalo@epgmbh.de http://www.epgmbh.de
Hello! I use samba-2.0.6 under Debian GNU/Linux. I have Win98 client. I find that if I try to copy (by Windows) a large file from client onto samba network drive, then this file corrupts almost for sure. Can anybody help me? Does anybody have this problem? Thanks! -- Serge Gavrilov
Running FreeBSD 4.8 (and in the past have run versions of FreeBSD on
this current server going back to 4.3 iirc)
Samba 2.2.8a (in the past have run previous versions)
Computer is a Athlon, with a highpoint raid controller, with 2 WD harddrives
RAID: ar0
Master: ad4 <WDC WD1200JB-00CRA0/16.06V16> ATA/ATAPI rev 5
Master: ad6 <WDC WD1200JB-00CRA0/16.06V16> ATA/ATAPI rev 5
The entire system lives on this raid, with about 100GB being shared via
Samba and Netatalk. All clients are XP and 2K.
My problem is that, sporadically, files living on the Samba share seem
to become corrupted. I've noticed this especially with large installer
files and large compressed files used by installers. for instance, I
was doing network installs of MS Office off the Samba share. I
installed Office on two new computers fine, and on the third computer I
get an error that Office1.cab (a roughly 290MB file) is corrupt. The
file changed--I copy it from the CD to the share again and the install
goes fine the next time i try it. the md5 of the two files is different
so I'm absolutely sure that the file definitely changed. It went
corrupt again after another install.
As another example, I had a mozilla installer sitting in a directory on
the share--no one but me would have touched it. Last used ~1 month ago.
Tried it today and it was corrupt.
I personally have only seen corruption in files of this type (installers
specifically) and am not sure if any other corruption exists. I've had
no complaints whnich is a good thing, and we regularly move a large
volume of files on and off the share via Netatalk (Quark and graphic
files) and they don't seem to get corrupt either. PC usage is generally
less intensive and limited to word files (I'm the only person that would
be installing stuff off the samba share)
I should note that I don't believe the harddisks are bad--this server
has been very stable and never goes down except for power outages. I've
noticed no corruption in any system files, or any files stored anywhere
but on this one share.
I should also add that I have a second smaller share (~2GB) on which our
accounting software runs--due to our accounting software requirements,
it has all oplocks turned off, and as far as i know there have been no
corruption issues.
Does anyone have a clue what the problem might be, or what I can test?
The problem with this is that it IS a sporadic problem, but it's
happened to me enough times that I'm sure it's real.
thanks much,
Scott