--- "Keith G. Murphy" <[EMAIL PROTECTED]> wrote:
> > I think he's referring to the phenomenon that
> I've seen on way too
> > many technical mailing lists: be a complete
> asshole and you'll get
> > the complete and undivided attention of multiple
> developers and power
> > users, all of of wh
David Collier-Brown -- Customer Engineering wrote:
>There are also some sharable filesystems that could
> result in two sambae sharing the same files: supposedy
> my employer sells one (:-))
:-)
Yes, I considered NFS, but only as as way to allow the two
Sambae to be on separate machines and s
Steve Langasek wrote:
> If oplock support is disabled, yes, you can expect two Samba
> installations to play nicely with locks on the same set of files. If
> oplocking is enabled, it might also be possible to make them behave,
> though this would at least require some symlink magic.
There
Reading through Jeremy's eagerly awaited discourse on oplocks/share
modes/locking, I read this bit :
> ... if you need simultaneous
> file access from a Windows and UNIX client you *must* have an
> application that is written to lock records correctly on both
> sides. Few applications are written
On Fri, Oct 25, 2002 at 01:44:03PM +1000, Matthew Hannigan wrote:
> Well, my specific example (which I noticed you avoided :-)
> was two sambas sharing the same files:
> You're not alone, everyone is ducking this question :-)
> Here it is again, just in case:
> Excellent, so two other
On Thu, Oct 24, 2002 at 08:15:08PM -0500, Steve Langasek wrote:
>
> Ah, but it doesn't really matter *what* the value of kernel oplocks is,
> if you don't have kernel support for oplocks. :) The only other option
My bad, I was confusing options 'op locks' and 'kernel op locks'
Still, it would b
Keith G. Murphy wrote:
> I think he's referring to the phenomenon that I've seen on way too
> many technical mailing lists: be a complete asshole and you'll get
> the complete and undivided attention of multiple developers and power
> users, all of of whom assert, while helping, that that's not a
On Fri, Oct 25, 2002 at 11:04:43AM +1000, Matthew Hannigan wrote:
> On Thu, Oct 24, 2002 at 10:44:28AM -0500, Steve Langasek wrote:
> > On Thu, Oct 24, 2002 at 01:08:10PM +1000, Matthew Hannigan wrote:
> > > And Solaris? At least they're autoconfigured to assume kernel oplocks
> > > according to t
On Thu, Oct 24, 2002 at 10:44:28AM -0500, Steve Langasek wrote:
> On Thu, Oct 24, 2002 at 01:08:10PM +1000, Matthew Hannigan wrote:
> > And Solaris? At least they're autoconfigured to assume kernel oplocks
> > according to testparm, and the docs say this is done only if the support
> > is there.
>
On Thu, Oct 24, 2002 at 06:36:10PM +, [EMAIL PROTECTED] wrote:
> On Thu, Oct 24, 2002 at 08:35:02PM +0200, Jelmer Vernooij wrote:
> > On Thu, Oct 24, 2002 at 05:48:49PM +, [EMAIL PROTECTED] wrote about 'Re:
>[Samba] Re: How Samba let us down':
> > > Ok, as
On Thu, Oct 24, 2002 at 01:08:10PM +1000, Matthew Hannigan wrote:
> On Thu, Oct 24, 2002 at 02:10:14AM +, [EMAIL PROTECTED] wrote:
> > On Wed, Oct 23, 2002 at 09:02:03PM -0500, Steve Langasek wrote:
> > > On Thu, Oct 24, 2002 at 11:38:55AM +1000, Matthew Hannigan wrote:
> > >
> > > > I have re
On Thu, 24 Oct 2002, Rashkae wrote:
> John, Please ignore this question from someone who probaby doesn't know
> enough to make sound statements, and who hasn't really followed the list
> closely lately
I choose to help, not ignore.
>
> Has there ever been an explanation found for the brief r
Andrew Bartlett wrote:
Philip Burrow wrote:
- Original Message -
From: Most of you
Cc: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Wednesday, October 23, 2002 10:14 PM
Subject: Re: [Samba] Re: How Samba let us down
etc etc
Well this one certainly roused you all.
Mu
> Philip Burrow wrote:
>
> - Original Message -
> From: Most of you
> Cc: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
> Sent: Wednesday, October 23, 2002 10:14 PM
> Subject: Re: [Samba] Re: How Samba let us down
>
> > etc etc
>
> Well this o
Somebody please drag this dead horse off the server.
PV
-Original Message-
From: Van Sickler, Jim [mailto:vansickj-eodc@;Kaman.com]
Sent: Thursday, October 24, 2002 1:10 PM
To: Samba-L (E-mail)
Subject: RE: [Samba] Re: How Samba let us down
> Philip Burrow wr
Ok, as promised, a brief explaination of oplocks, share modes
and locking.
When a client opens a file it can request an "oplock" or file
lease. This is (to simplify a bit) a guarentee that no one else
has the file open simultaneously. It allows the client to not
send any updates on the file to the
On Thu, Oct 24, 2002 at 05:48:49PM +, [EMAIL PROTECTED] wrote about 'Re: [Samba]
Re: How Samba let us down':
> Ok, as promised, a brief explaination of oplocks, share modes
> and locking.
> [...]
Mind if I add this to the docs?
Jelmer
--
To unsubscribe from this list
On Thu, Oct 24, 2002 at 08:35:02PM +0200, Jelmer Vernooij wrote:
> On Thu, Oct 24, 2002 at 05:48:49PM +, [EMAIL PROTECTED] wrote about 'Re: [Samba]
>Re: How Samba let us down':
> > Ok, as promised, a brief explaination of oplocks, share modes
> > and locking.
>
John, Please ignore this question from someone who probaby doesn't know
enough to make sound statements, and who hasn't really followed the list
closely lately
Has there ever been an explanation found for the brief rash of people who
had tidbits of Samba log file data inserted in their network
Regarding tests you can perform on the windows side:
A couple of months ago, a samba user wrote in this group explaining
that the easiest way to reproduce op-lock break timeouts was to select
10 or 20 so MS Word files and open them all once. (I've tried multiuser
test programs which lock regio
On Thu, Oct 24, 2002 at 07:34:19AM +0200, Walter Mautner wrote:
> As far as I know, "oplocks" are extensions to common file locks.
> In fact, whenever a oplock is set, also a conventional lock
> request is sent to the underlying non-smb locking system, and only
> if this one doesn't report it as
On Thu, Oct 24, 2002 at 11:38:55AM +1000, Matthew Hannigan wrote:
..
> I did have a look at the docs really, but
> textdocs/UNIX-SMB.txt for instance says that "Unix has no
> simple way of implementing opportunistic locking, and
> currently Samba has no support for it."
>
> Which is out of date
On Thu, Oct 24, 2002 at 02:10:14AM +, [EMAIL PROTECTED] wrote:
> On Wed, Oct 23, 2002 at 09:02:03PM -0500, Steve Langasek wrote:
> > On Thu, Oct 24, 2002 at 11:38:55AM +1000, Matthew Hannigan wrote:
> >
> > > I have read in the docs that Samba locks and Unix locks
> > > _DO_ notice each other,
On Wed, Oct 23, 2002 at 09:02:03PM -0500, Steve Langasek wrote:
> On Thu, Oct 24, 2002 at 11:38:55AM +1000, Matthew Hannigan wrote:
> > On Wed, Oct 23, 2002 at 02:14:41PM -0700, Marc Jacobsen wrote:
> > > [ ... ]
> > > Similarly, record locks and share mode locks from SMB clients are both
> > > ig
On Thu, Oct 24, 2002 at 11:38:55AM +1000, Matthew Hannigan wrote:
> On Wed, Oct 23, 2002 at 02:14:41PM -0700, Marc Jacobsen wrote:
> > [ ... ]
> > Similarly, record locks and share mode locks from SMB clients are both
> > ignored by NFS clients/other UNIX processes (with the possible exception
>
On Wed, Oct 23, 2002 at 02:14:41PM -0700, Marc Jacobsen wrote:
> [ ... ]
> Similarly, record locks and share mode locks from SMB clients are both
> ignored by NFS clients/other UNIX processes (with the possible exception
> of newer Linux systems, they might actually enforce share mode locks).
>
From: [EMAIL PROTECTED] [mailto:samba-admin@;lists.samba.org]On
Behalf Of John H Terpstra
Sent: Wednesday, October 23, 2002 4:39 PM
To: Philip Burrow
Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: Re: [Samba] Re: How Samba let us down
On Wed, 23 Oct 2002, Philip Burrow wrote:
Philip,
Those of u
John H Terpstra wrote:
> Jay Ts wrote:
> > John H Terpstra wrote:
> > >
> > > For the record, I thouroughly test samba pre-releases before we ever ship.
> > > To the best of my knowledge, NOT ONE version of samba we have released
> > > ever CAUSED (or resulted in) file/data corruption. If I sound d
consuming, and is voluntary.
- John T.
> - Original Message -
> From: Most of you
> Cc: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
> Sent: Wednesday, October 23, 2002 10:14 PM
> Subject: Re: [Samba] Re: How Samba let us down
>
> > etc etc
>
> Well t
Philip Burrow wrote:
> - Original Message -
> From: Most of you
> Cc: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
> Sent: Wednesday, October 23, 2002 10:14 PM
> Subject: Re: [Samba] Re: How Samba let us down
>
> > etc etc
>
> Well this one certainl
Philip Burrow wrote:
>
> - Original Message -
> From: Most of you
> Cc: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
> Sent: Wednesday, October 23, 2002 10:14 PM
> Subject: Re: [Samba] Re: How Samba let us down
>
> > etc etc
>
> Well this one
Title: RE: [Samba] Re: How Samba let us down
I tend to focus on absurdities. They lead to interesting results.
-Original Message-
From: Philip Burrow [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, October 23, 2002 5:22 PM
Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: Re: [Samba] Re
- Original Message -
From: Most of you
Cc: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Wednesday, October 23, 2002 10:14 PM
Subject: Re: [Samba] Re: How Samba let us down
> etc etc
Well this one certainly roused you all.
Must it be the case that you all jump in t
On Wed, Oct 23, 2002 at 02:14:41PM -0700, Marc Jacobsen wrote:
> This next statement from John Terpstra seems a bit strong to me, see the
> counter example below from just a few weeks ago. Not to badmouth John,
> or Samba, just to add some more information to the conversation.
>
> What about th
As I understand it, concurrent access from SMB clients and NFS clients
(or other UNIX processes) can cause corruption when oplocks is turned on
(unless your UNIX supports kernel oplocks and you use them - only some
Linux and Irix versions support them I believe). Turning off oplocks
might redu
On Wed, Oct 23, 2002 at 01:26:15PM -0700, Jay Ts wrote:
> John H Terpstra wrote:
> >
> > Both ways. Remember file/data corruption is a death issue. We do NOT ship
> > if we see it is broken and we are PARANOID about integrity. Also, remember
> > that just because it works does not mean it is not b
John H Terpstra wrote:
>
> Both ways. Remember file/data corruption is a death issue. We do NOT ship
> if we see it is broken and we are PARANOID about integrity. Also, remember
> that just because it works does not mean it is not broken. Oops, did I say
> PARANOID?
> [...]
> Also remember our uni
On Wed, 23 Oct 2002, Jay Ts wrote:
> John H Terpstra wrote:
> >
> > For the record, I thouroughly test samba pre-releases before we ever ship.
> > To the best of my knowledge, NOT ONE version of samba we have released
> > ever CAUSED (or resulted in) file/data corruption. If I sound defensive -
>
On Thu, Oct 24, 2002 at 06:36:26AM +0930, Richard Sharpe wrote:
>
> In my opinion, while it is possible to do what you say, that is not how
> you will detect corruption. Corruption of the sort you mention will be
> detected very quickly in normal tests.
>
> The sort of corruption I think we shoul
On Wed, 23 Oct 2002, Jay Ts wrote:
> Esh, Andrew wrote:
> > Here at Tricord, we run Samba through some pretty intense tests, as well.
> > Since we are a file system producer, we focus on corruption bugs. We haven't
> > found any in Samba,
>
> Since I've been curious about this anyway, I might go a
On Wed, Oct 23, 2002 at 02:34:28PM -0500, Esh, Andrew wrote:
> We regularly do large file Copy-Paste tests with files between 30G and 60G.
> We have yet to see a problem.
>
> Tricord's market is Network Attached Storage, and our product is a file
> system. Samba is the main interface between our m
On Wed, 23 Oct 2002, Jay Ts wrote:
> Esh, Andrew wrote:
> > Here at Tricord, we run Samba through some pretty intense tests, as well.
> > Since we are a file system producer, we focus on corruption bugs. We haven't
> > found any in Samba,
>
> Since I've been curious about this anyway, I might go
Title: RE: [Samba] Re: How Samba let us down
We regularly do large file Copy-Paste tests with files between 30G and 60G. We have yet to see a problem.
Tricord's market is Network Attached Storage, and our product is a file system. Samba is the main interface between our market and our
Esh, Andrew wrote:
> Here at Tricord, we run Samba through some pretty intense tests, as well.
> Since we are a file system producer, we focus on corruption bugs. We haven't
> found any in Samba,
Since I've been curious about this anyway, I might go ahead and check:
Do you (And J. Terpstra, and o
John H Terpstra wrote:
>
> For the record, I thouroughly test samba pre-releases before we ever ship.
> To the best of my knowledge, NOT ONE version of samba we have released
> ever CAUSED (or resulted in) file/data corruption. If I sound defensive -
> that's is exactly correct because file corrup
Title: RE: [Samba] Re: How Samba let us down
Here at Tricord, we run Samba through some pretty intense tests, as well. Since we are a file system producer, we focus on corruption bugs. We haven't found any in Samba, other than a rather famous Microsoft Word bug that also occurs on Wi
Jay,
For the record, I thouroughly test samba pre-releases before we ever ship.
To the best of my knowledge, NOT ONE version of samba we have released
ever CAUSED (or resulted in) file/data corruption. If I sound defensive -
that's is exactly correct because file corruption is a DEATH issue!
Plea
Jeremy Allison ([EMAIL PROTECTED]) wrote:
> Jay Ts wrote:
> >
> > > The corruption might be related to oplocks. I'm doing
Just to keep myself out of more trouble today, I'd like
to point out that I didn't write the above. ;-)
> File corruption is treated as a drop everything - priority
> 1 bug
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 be issuing a patch *immediately*.
That's not to say
Steve Langasek wrote:
> Jay Ts wrote:
>
> > kernel oplocks are for synchronizing SMB clients and
> > local Unix processes. If you have no processes on linux
> > accessing the files, then it's probably safe to disable them.
> > But, if you are using Linux, the only way you should have
> > kernel op
On Wed, Oct 23, 2002 at 05:25:56AM -0700, Jay Ts wrote:
> kernel oplocks are for synchronizing SMB clients and
> local Unix processes. If you have no processes on linux
> accessing the files, then it's probably safe to disable them.
> But, if you are using Linux, the only way you should have
> ker
> -Original Message-
> From: Bradley W. Langhorst [mailto:brad@;langhorst.com]
> i use acls - people like them..
> i wouldn't think there'd be a particular performace hit with them
> though...
I use ACLs. They work fine for me, but then again I've only got about 30
clients.
> another
Chris:
First of all let me say that your implementation of Samba is orders of
magnitude above mine, however I have seen some problems similar to yours. I
second the advice about the WINS server. When I have not had this set up
properly (or nmbd has died for some reason) I see all kinds of odd bro
On Wed, 2002-10-23 at 04:54, Chris de Vidal wrote:
>
> You could be right here. The author in the link above
> indicated that it might be a problem with small RAID 5
> random read/writes. Know how to see I/Os/sec on
> Linux, by chance? Bonnie++? I'm still learning about
> Linux through experi
Chris de Vidal wrote:
>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.
>
> While this is a great way to increase speed,
> A. It's plenty fast on the NT, Netware, and other
> Samba servers. In
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
--- Bartlomiej Solarz-Niesluchowski
> >The actual queues are on an NT server. This server
> >merely acts as a large spool area. Are you using
> >Samba as the spool area only or using Samba
> printing
> >support?
>
> I use only samba printing support (all printers are
> net printers
> HP4000N/4
Thank you for responding. You win a gold star for
actually reading my email and not jumping to
conclusions (-:
--- Tristan Ball <[EMAIL PROTECTED]> wrote:
> I think the 7580 might be a mistake. The card has
> only 2meg of cache (read: f*ck all).
The amount of RAM is not an apples-to-apples
compa
--- Bartlomiej Solarz-Niesluchowski
<[EMAIL PROTECTED]> wrote:
> At 08:13 2002-10-23, you wrote:
>
> >The printers were missing some of the records sent
> to
> >them to print, something that had never happened
> with
> >Netware. Every time the missing records were
> >different. Occasionally, it
--- Chris de Vidal <[EMAIL PROTECTED]> wrote:
> --- tim smith <[EMAIL PROTECTED]> wrote:
> > err are you asking for help, or just wasting our
> > time?
>
> Read the first paragraph of my email, please.
It said:
"Before you read this, I want to state (for reasons
listed below) that I don't expect
--- tim smith <[EMAIL PROTECTED]> wrote:
> err are you asking for help, or just wasting our
> time?
Read the first paragraph of my email, please.
/dev/idal
__
Do you Yahoo!?
Y! Web Hosting - Let the expert host your web site
http://webhosting.yahoo
61 matches
Mail list logo
