Samba3 rc3 - traverse_fn_delete - listing print queues still off and on

daniel.jarboe at custserv.com daniel.jarboe at custserv.com
Wed Dec 17 21:01:38 GMT 2003


Jerry, I think I have bigger problems... just ran tdbtorture on a SLES8
s/390 server and it quickly spewed failure messages left and right:

tdb_brlock failed (fd=3) at offset 45220 rw_type=1 lck_type=13: Resource
temporarily unavailable
tdb_brlock failed (fd=3) at offset 45220 rw_type=1 lck_type=13: Resource
temporarily unavailable
tdb_brlock failed (fd=3) at offset 45220 rw_type=1 lck_type=13: Resource
temporarily unavailable
tdb_brlock failed (fd=3) at offset 45220 rw_type=1 lck_type=13: Resource
temporarily unavailable
tdb_brlock failed (fd=3) at offset 45220 rw_type=1 lck_type=13: Resource
temporarily unavailable
tdb_brlock failed (fd=3) at offset 1080 rw_type=1 lck_type=13: Resource
temporarily unavailable
tdb_brlock failed (fd=3) at offset 45220 rw_type=1 lck_type=13: Resource
temporarily unavailable
tdb_brlock failed (fd=3) at offset 1080 rw_type=1 lck_type=13: Resource
temporarily unavailable
tdb_brlock failed (fd=3) at offset 1080 rw_type=1 lck_type=13: Resource
temporarily unavailable
tdb_brlock failed (fd=3) at offset 43852 rw_type=1 lck_type=13: Resource
temporarily unavailable
tdb_brlock failed (fd=3) at offset 43852 rw_type=1 lck_type=13: Resource
temporarily unavailable
tdb_brlock failed (fd=3) at offset 43852 rw_type=1 lck_type=13: Resource
temporarily unavailable
tdb_brlock failed (fd=3) at offset 43852 rw_type=1 lck_type=13: Resource
temporarily unavailable
tdb_brlock failed (fd=3) at offset 43852 rw_type=1 lck_type=13: Resource
temporarily unavailable
tdb_brlock failed (fd=3) at offset 43852 rw_type=1 lck_type=13: Resource
temporarily unavailable
tdb_brlock failed (fd=3) at offset 43852 rw_type=1 lck_type=13: Resource
temporarily unavailable

etc...

This is with 3.0.1... I will check out 2.2.8a tomorrow.

I noticed there was no spinlock ifdef for S390, perhaps there needs to
be one?

~ Daniel

> -----Original Message-----
> From: Gerald (Jerry) Carter [mailto:jerry at samba.org] 
> Sent: Friday, December 12, 2003 10:21 AM
> To: Jarboe, Daniel - Data Center Operations 
> <daniel.jarboe at custserv.com>
> Cc: samba-technical at lists.samba.org
> Subject: Re: Samba3 rc3 - traverse_fn_delete - listing print 
> queues still off and on
> 
> 
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> daniel.jarboe at custserv.com wrote:
> 
> | Hrm, now that I've upgraded to rc1 the jobs don't show up
> | at all in the printer window.
> 
> | Does this line strike you as normal:
> | [2003/12/10 07:14:36, 5] tdb/tdbutil.c:tdb_log(724)
> |   tdb(unnamed): tdb_brlock failed (fd=24) at offset 4 rw_type=1
> | lck_type=13: Resource temporarily unavailable
> 
> Maybe....
> 
> | This is not related, but over time (a few hours
> | of use) smbstatus inevitable reports rec_read bad
> | magic 0x42424242 in sessionid.tdb. Maybe I'm running
> | up against some byteorder problems?  I may have to
> | bail on 3 and go back to testing on 2.2.8a :(.
> 
> I wouldn't think so, but anything is possible.
> smbd in 3.0 has code to remove corrupt tdbs on
> open and then abort so that the next open will
> recreate the tdb file automatically.
> 
> |
> | Here's the machine log with the printer jobs window open for two
> | minutes...
> 
> I'll have to work on this some more next week.
> 
> 
> 
> 
> cheers, jerry
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.1 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
> 
> iD8DBQE/2dzwIR7qMdg1EfYRAjw1AJ9EimB8sXQ/QfUyRls+gFCZs39nnACgqMIr
> sDZVMJNe9UsECmLozo3pXLo=
> =6ohH
> -----END PGP SIGNATURE-----
> 
> 
> 

-----------------------------------------------------------------------

This message is the property of Time Inc. or its affiliates. It may be
legally privileged and/or confidential and is intended only for the use
of the addressee(s). No addressee should forward, print, copy, or
otherwise reproduce this message in any manner that would allow it to be
viewed by any individual not originally listed as a recipient. If the
reader of this message is not the intended recipient, you are hereby
notified that any unauthorized disclosure, dissemination, distribution,
copying or the taking of any action in reliance on the information
herein is strictly prohibited. If you have received this communication
in error, please immediately notify the sender and delete this message.
Thank you.



More information about the samba-technical mailing list