-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
O.K. I'm going to run this test again with logging up around 10 somewhere on a clean install; hopefully that'll allow me to track it down.
I should have more information later today.
Jeremy Allison wrote: | On Mon, Feb 28, 2005 at 12:56:47PM -0800, Tom Dickson wrote: | |>-----BEGIN PGP SIGNED MESSAGE----- |>Hash: SHA1 |> |>I was running a netbench performance test against Samba 3.0.11, and the |>test has |>not been able to complete fully. |> |>The samba logs contain lines such as this: |> |>[2005/02/28 11:35:23, 1] smbd/service.c:make_connection_snum(645) |>~ slave16 (192.168.133.116) connect to service netbench initially as user |>BENCHLAB+slave16 (uid=10016, gid=10001) (pid 6599)[2005/02/28 11:41:14, 0] |>tdb/tdbutil.c:tdb_log(725) |>~ tdb(/var/lib/samba/locking.tdb): tdb_lock failed on list 86 ltype=0 |>(Resource |>deadlock avoided) |>[2005/02/28 11:45:48, 0] tdb/tdbutil.c:tdb_log(725) |>~ tdb(/var/lib/samba/locking.tdb): tdb_lock failed on list 41 ltype=0 |>(Resource |>deadlock avoided) |>[2005/02/28 11:51:15, 0] tdb/tdbutil.c:tdb_log(725) |>~ tdb(/var/lib/samba/locking.tdb): tdb_lock failed on list 86 ltype=0 |>(Resource |>deadlock avoided) |> |>Does this mean that we need to increase some parameter? Is there a known |>failure |>in this area, or could it be a misconfiguration of the clients? |> |>I'll be rerunning this test with more detailed logging as I try to track |>this |>issue down. |> |>Kernel 2.4.29 |>Samba 3.0.11 |>XFS filesystem | | | Not a current known problem. As far as I know this should work. | | Jeremy. | | . | -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFCI5Yu2dxAfYNwANIRAgqCAKCr2MdMNcj/YWnZMza59ZNQaisGzACfYd5O tseEvMBzm7Cf6f4TteNuUDg= =/dg/ -----END PGP SIGNATURE----- -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
