I've been seeing a lot of tdb problems during our SuSE trial when it comes to Samba. Over time a tdb or two inevitably becomes corrupt, sometimes in just an hour or two. I ran tdbtorture, a tool that comes with the samba source, and got errors left and right. On intel, the tdbtorture suite just runs for a while and prints OK. Well, on s/390 immediately there are a plethora of messages like:
tdb_brlock failed (fd=3) at offset 11752 rw_type=1 lck_type=13: Resource temporarily unavailable tdb_brlock failed (fd=3) at offset 11752 rw_type=1 lck_type=13: Resource temporarily unavailable tdb_brlock failed (fd=3) at offset 11752 rw_type=1 lck_type=13: Resource temporarily unavailable tdb_brlock failed (fd=3) at offset 11752 rw_type=1 lck_type=13: Resource temporarily unavailable tdb_brlock failed (fd=3) at offset 11752 rw_type=1 lck_type=13: Resource temporarily unavailable tdb_brlock failed (fd=3) at offset 11752 rw_type=1 lck_type=13: Resource temporarily unavailable tdb_brlock failed (fd=3) at offset 11752 rw_type=1 lck_type=13: Resource temporarily unavailable I looked in tdb/spinlock.c and saw a bunch of architecture-specific #ifdefs, but nothing S/390ish. Should there be one? ~ Daniel ----------------------------------------------------------------------- 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.
