--- 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 go
--- David Brodbeck <[EMAIL PROTECTED]> wrote:
> It's rather
> shocking to me that SMB reacts
> to poorly to network problems, but I realize there's
> not much Samba can do
> about the crummy protocol design. ;)
There is one thing: (Now I'm beating a dead horse on
this, so I'll shut up and see what
--- "Green, Paul" <[EMAIL PROTECTED]> wrote:
> My opinion is that the "right fix" is for anyone who
> is experiencing data
> corruption of any sort, whether with oplocks on,
> off, or sideways, to work
> with the Samba team to come up with a reproducible
> test case so that we can
> root cause the
wrote:
> Jeremy Allison ([EMAIL PROTECTED]) wrote:
> > Chris de Vidal wrote:
> >
> > > Still, wouldn't you welcome documentation
> advising
> > > people of potential corruption? I think we both
> agree
> > > that there is no guarantee that everyone&
--- [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
--- 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.
&
--- [EMAIL PROTECTED] wrote:
> On Thu, Oct 24, 2002 at 04:43:53AM -0700, Chris de
> Vidal wrote:
>
> > OpLocks were indeed causing corruption; we only
> turned
> > them off, made no other changes, and have no more
> > corruption, as I reported yesterday. Would
--- "Bradley W. Langhorst" <[EMAIL PROTECTED]> wrote:
> On Thu, 2002-10-24 at 09:43, Chris de Vidal wrote:
> > If preventing file corruption is a "drop
> everything -
> > priority 1 bug" (quoting Jeremy), it should either
> be
> > documente
--- "Bradley W. Langhorst" <[EMAIL PROTECTED]> wrote:
> the oplock problem with access databases is well
> known...
> I don't think samba alone can fix it.
> (somebody prove me wrong :)
Samba alone probably cannot fix it. I have since
learned it can also be a problem on NT. Jeremy says,
"file c
--- 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 seldom
--- [EMAIL PROTECTED] wrote:
> On Wed, Oct 23, 2002 at 05:25:56AM -0700, Jay Ts
> wrote:
> >
> > > The corruption might be related to oplocks. I'm
> doing
>
> File corruption is treated as a drop everything -
> priority
> 1 bug in Samba. If this were a generic problem known
> with
> 2.2.6 we'd b
My first post, for reference:
http://marc.theaimsgroup.com/?l=samba&m=103535378916869&w=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
--- Michael Smirnov <[EMAIL PROTECTED]> wrote:
> When I use Samba with option
>write cache size = 262144
> my antivirus monitoring programs(AVP Monitor) do not
> catch viruses on Samba network drive,
> but successfully catch viruses, after I delete this
> options and restart Samba!
This _may_
The new NT server has a bad HD, so we have a repreive
temporarily and perhaps we can still work this problem
out and still use Samba (:
--- Mathew McKernan <[EMAIL PROTECTED]>
wrote:
> By the look of it, the reason why it is so slow is
> the fact that you may not
> be running a WINS Server. We had
Before you read this, I want to state (for reasons
listed below) that I don't expect an answer (advice is
welcomed, but please read this email carefully before
answering). I'm sharing this with the community with
the hope that better software results from our sad
experience...
BACKGROUND
I've be
15 matches
Mail list logo
