jra == jra [EMAIL PROTECTED] writes:
jra Clients commonly ignore oplock breaks because of network problems
jra (borderline hubs etc.). Many people are suffering from network
jra hardware that performs adequately in light use situations and
jra fails under heavy load. I myself have ended up
On Fri, Nov 22, 2002 at 08:44:34AM -0800, Russell Senior wrote:
jra == jra [EMAIL PROTECTED] writes:
jra Clients commonly ignore oplock breaks because of network problems
jra (borderline hubs etc.). Many people are suffering from network
jra hardware that performs adequately in light use
David == David W Chapman [EMAIL PROTECTED] writes:
jra Clients commonly ignore oplock breaks because of network problems
jra (borderline hubs etc.). Many people are suffering from network
jra hardware that performs adequately in light use situations and
jra fails under heavy load. I myself have
David Duplex problems are a simple example like setting full-duplex
David on a half-duplex switch might.
David A bad cable or NIC could cause intermitten problem as well.
David Yes packets would get retransmitted, but who's to say the
David retransmitted packets won't get dropped as well?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Clients commonly ignore oplock breaks because of network
problems (borderline hubs etc.). Many people are suffering
from network hardware that performs adequately in light
use situations and fails under heavy load. I myself have
ended up junking
--- Claudia Moroder
[EMAIL PROTECTED] wrote:
what does samba if a client locks a byte range
behind the end of the file ?
This could be important because it looks like many
'corruption' problems
happern with foxpro files.
And we are using foxpro files.. hmm.
/dev/idal
P.S. haven't gotten a
On Thu, Oct 31, 2002 at 07:28:44PM +0100, Claudia Moroder wrote:
Hello,
what does samba if a client locks a byte range behind the end of the file ?
This could be important because it looks like many 'corruption' problems
happern with foxpro files.
Samba adds the locks. It doesn't care if
Chris de Vidal wrote:
--- Claudia Moroder wrote:
This could be important because it looks like many
'corruption' problems happern with foxpro files.
And we are using foxpro files.. hmm.
/dev/idal
P.S. haven't gotten a chance to try turning oplocks on
for bug testing; Management is
Jay Ts [mailto:jay;jayts.cx] said: [excerpt]
I know this is a tough issue, and I'm not sure what I'd
do if I were in the driver's seat. Perhaps as a
minimum, adding some documentation to the /docs directory,
as Chris suggests, and also putting lines in the example
smb.conf files showing how
You hit it _on_the_nose_ here. We wish someone had
commented in the smb.conf, the manpages, the
documents, ANYWHERE, about potential
corruption/slowness with large database files and
OpLocks. There is a chance we would have been spared
grief.
/dev/idal
--- Jay Ts [EMAIL PROTECTED] wrote:
--- Neil Hoggarth [EMAIL PROTECTED]
wrote:
On Thu, 24 Oct 2002, Chris de Vidal wrote:
I'd be happy to let the group know. I'm not
positive
we'll reenable anything but kernel oplocks,
though.
We have work to do.
The kernel oplocks parameter affects how Unix
processes accessing the
On Mon, Oct 28, 2002 at 02:36:00PM -0800, Chris de Vidal wrote:
The team probably would have to install Elixir's Opus
and process large flat db files (Fox Pro, I think)
with multiple processes on multiple servers... in
other words, it probably isn't going to happen. The
corruption will
--- [EMAIL PROTECTED] wrote:
The oplock code in Samba has been *heavily* tested.
The one thing we cannot fix is clients ignoring
oplock
break requests. If you can show a problem occurring
when clients are *not* ignoring oplock break
requests then
it's a Samba logic bug and we'll jump on it
--- Jay Ts [EMAIL PROTECTED] wrote:
* The corruption was missing records. It would
interrupt the print process and the Opus analysis
indicated hundreds of records were missing. It
would
happen in random places in print files (hundreds
of
megs to gigs in size), and seldomly would not
My first post, for reference:
http://marc.theaimsgroup.com/?l=sambam=103535378916869w=2
When the new NT server's hard drive died, we decided
to keep hobbling along on Samba. Meanwhile, my
supervisor was searching around on OpLock issues on
Google and he saw other people that were having
similar
15 matches
Mail list logo
