Which revision of rhel4 samba are you using? 4E.6 contains patches to
prevent smbd from borking a system like you describe.
grep samba /var/log/rpmpkgs
or
rpm -q samba
If you're on a lower rpm package revision than .6, you should try the
upgrade. The version previous to 4E.6 was 4E.2 if
On Tue, 28 Feb 2006, Fermin Molina wrote:
Just to add -- our fcntl locking issue is on Linux, we've
seen it on 2.6.9, 2.6.13.1 and 2.6.15.3, running Mandrake 10.2.
locking.tdb is on a local disk. All smbd child processes are
blocked on apparently the same fcntl when it happens.
Hmmm...ok.
On Wed, 2006-03-01 at 09:57 +, Matt Johnson wrote:
On Tue, 28 Feb 2006, Fermin Molina wrote:
Just to add -- our fcntl locking issue is on Linux, we've
seen it on 2.6.9, 2.6.13.1 and 2.6.15.3, running Mandrake 10.2.
locking.tdb is on a local disk. All smbd child processes are
blocked
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Fermin Molina wrote:
I don't know exactly, but when I moved the information
from NFS servers to local storage, the problems disappeared.
Samba assumes posix locking semantics on the filesystem.
NFS locking is broken. You might try setting
On Wed, 2006-03-01 at 07:45 -0600, Gerald (Jerry) Carter wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Fermin Molina wrote:
I don't know exactly, but when I moved the information
from NFS servers to local storage, the problems disappeared.
Samba assumes posix locking
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Fermin Molina wrote:
Samba assumes posix locking semantics on the filesystem.
NFS locking is broken. You might try setting
'strict locking = no'. If that doesn't work, you might
try 'posix locking = no' just as a test.
Well, but I think the
On Wed, 1 Mar 2006, Gerald (Jerry) Carter wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Fermin Molina wrote:
I don't know exactly, but when I moved the information
from NFS servers to local storage, the problems disappeared.
Samba assumes posix locking semantics on the filesystem.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Matt Johnson wrote:
On Wed, 1 Mar 2006, Gerald (Jerry) Carter wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Fermin Molina wrote:
I don't know exactly, but when I moved the information
from NFS servers to local storage, the problems
On Wed, 1 Mar 2006, Gerald (Jerry) Carter wrote:
On Wed, 1 Mar 2006, Gerald (Jerry) Carter wrote:
Samba assumes posix locking semantics on the filesystem.
NFS locking is broken. You might try setting
'strict locking = no'. If that doesn't work, you might
try 'posix locking = no' just as a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Matt Johnson wrote:
Hm, fun... Okay. I guess that making the same host
serve both NFS and CIFS off the same physical volume
is probably the best ultimate solution? (This is the
direction we are heading in, but right now, not
quite in a position
, February 28, 2006 3:25 PM
Subject: Re: [Samba] hanging smbd(s) revisited
On Tue, Feb 28, 2006 at 01:30:40PM -0500, William Jojo wrote:
So we've gone back to 3.0.20 and we're stable again. I should indicate
that
it's 3.0.20 with patches 9484, 9481 and 9456 to fix Win98 dir loop,
excel
On Wed, Mar 01, 2006 at 03:22:44PM +0100, Fermin Molina wrote:
Well, but I think the problem isn't located in the locking of NFS files;
smbd daemons always get stalled doing a lock of local locking.tdb
file. Then, must be broken the ext3 locking? In any case, maybe it's
broken all locking
On Wed, 1 Mar 2006, Gerald (Jerry) Carter wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Matt Johnson wrote:
Hm, fun... Okay. I guess that making the same host
serve both NFS and CIFS off the same physical volume
is probably the best ultimate solution? (This is the
direction we are
Matt,
To reiterate... the fcntl64 spins in a blocking wait, so we never see an
error unfortunately.
spins in a blocking wait? What does that mean? Either it is spinning
(chewing cpu) or its in a blocking wait (and not chewing cpu). If its
doing both then its a kernel bug.
If this is Linux,
- Original Message -
From: William Jojo [EMAIL PROTECTED]
To: Gerald (Jerry) Carter [EMAIL PROTECTED]
Cc: samba@lists.samba.org; Andrew Tridgell [EMAIL PROTECTED]; Jeremy
Allison [EMAIL PROTECTED]
Sent: Saturday, February 25, 2006 11:38 AM
Subject: Re: [Samba] hanging smbd(s) revisited
On Sat, 2006-02-25 at 16:58 +, Matt Johnson wrote:
On Sat, 25 Feb 2006, Gerald (Jerry) Carter wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Matt Johnson wrote:
Hi,
Just to add -- our fcntl locking issue is on Linux, we've
seen it on 2.6.9, 2.6.13.1 and 2.6.15.3,
On Tue, Feb 28, 2006 at 01:30:40PM -0500, William Jojo wrote:
So we've gone back to 3.0.20 and we're stable again. I should indicate that
it's 3.0.20 with patches 9484, 9481 and 9456 to fix Win98 dir loop, excel
shared workbook and ACLs (not necessarily in that order).
Since the problem
: [Samba] hanging smbd(s) revisited
On Tue, Feb 28, 2006 at 01:30:40PM -0500, William Jojo wrote:
So we've gone back to 3.0.20 and we're stable again. I should indicate
that
it's 3.0.20 with patches 9484, 9481 and 9456 to fix Win98 dir loop,
excel
shared workbook and ACLs (not necessarily
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
William Jojo wrote:
filemon summary shows fd 3 with 250MB/s for a process
that's not running any more and IBM cannot tell me why that
happens. (we're AIX 5.2 TL-08-1 and 3.0.21b) So that's why
I haven't been that suspicious of Samba.
I wonder
Hi,
Just to add -- our fcntl locking issue is on Linux, we've seen it on
2.6.9, 2.6.13.1 and 2.6.15.3, running Mandrake 10.2. locking.tdb is on a
local disk. All smbd child processes are blocked on apparently the same
fcntl when it happens.
Cheers
Matt
On Sat, 25 Feb 2006, Gerald (Jerry)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Matt Johnson wrote:
Hi,
Just to add -- our fcntl locking issue is on Linux, we've
seen it on 2.6.9, 2.6.13.1 and 2.6.15.3, running Mandrake 10.2.
locking.tdb is on a local disk. All smbd child processes are
blocked on apparently the same fcntl
On Sat, 25 Feb 2006, Gerald (Jerry) Carter wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Matt Johnson wrote:
Hi,
Just to add -- our fcntl locking issue is on Linux, we've
seen it on 2.6.9, 2.6.13.1 and 2.6.15.3, running Mandrake 10.2.
locking.tdb is on a local disk. All smbd child
On Sat, 25 Feb 2006, Gerald (Jerry) Carter wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Matt Johnson wrote:
Hi,
Just to add -- our fcntl locking issue is on Linux, we've
seen it on 2.6.9, 2.6.13.1 and 2.6.15.3, running Mandrake 10.2.
locking.tdb is on a local disk. All smbd child
- Original Message -
From: Matt Johnson [EMAIL PROTECTED]
To: samba@lists.samba.org
Sent: Friday, February 24, 2006 11:21 AM
Subject: [Samba] hanging smbd(s) revisited
Back in December, I was having problems with fcntl64 locks hanging.
On Thu, 15 Dec 2005, Matt Johnson wrote:
On
Christian,
Have you seen any more problems with your SMBD(s) hanging after setting
your machine password timeout = 0 ??
We have been having a similar problem with the hanging smbd(s) and
eventually samba just stops responding. Just curious if you have had
additional problems after making
Christian,
Well the problem seems similar somewhat, and I'm willing to try it to
get rid of this problem. Hopefully it will work for us too.
Matt
Masopust, Christian wrote:
Hi Matt,
our server now runs fine without any problems since mid of december
(with machine password timeout
send
me instructions :-)))
-Original Message-
From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
ba.org] On Behalf Of Masopust Christian
Sent: Thursday, December 15, 2005 4:45 PM
To: Gerald (Jerry) Carter
Cc: samba@lists.samba.org
Subject: RE: [Samba] hanging smbd(s
On Thu, 15 Dec 2005, Masopust Christian wrote:
dear all,
the following problem occurs periodically (appr. once a week) here:
the number of smbd(s) will dramatically rise (up to 500 and more...)
when having a look what the proccesses are doing i only see that they
are waiting for getting a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Masopust Christian wrote:
dear all,
the following problem occurs periodically (appr. once a week) here:
the number of smbd(s) will dramatically rise (up to 500
and more...) when having a look what the proccesses are doing
i only see that
On Thu, 15 Dec 2005, Gerald (Jerry) Carter wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Matt Johnson wrote:
Yes, this is a similar class of problem to that which I'm seeing with
locking.tdb on fd=14 -- exactly the same lock-hang behaviour being
raised in tdb_brlock.
We just fixed
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Matt Johnson wrote:
On Thu, 15 Dec 2005, Gerald (Jerry) Carter wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Matt Johnson wrote:
Yes, this is a similar class of problem to that which I'm seeing with
locking.tdb on fd=14 -- exactly the
On Thu, 15 Dec 2005, Gerald (Jerry) Carter wrote:
HmmI'm not sure if the bug was strictly in the new oplock
implement (post 3.0.20) but it doesn sound like what you are
describing. If you want to the the SAMBA_3_0_RELEASE branch
and see that would be appreciated. The final 3.0.21 release
the following problem occurs periodically (appr. once a week) here:
the number of smbd(s) will dramatically rise (up to 500
and more...) when having a look what the proccesses are doing
i only see that they are waiting for getting a lock:
fcntl64(4, F_SETLKW64, {type=F_WRLCK,
33 matches
Mail list logo
