Jeremy Allison wrote: >>Then it might be an intermittent bug in Veritas. What system call is >>smbd hanging on ? smbd should never hang in the D wait state unless >>it's a filesystem bug.
I am beginning to believe that this could make sense. Let me emphasize that ./private/secrets.tdb is shared between two samba servers (via clustered vxfs) that are running independently. Only one server runs nmbd at a time as veritas cluster server fails nmbd over between servers as needed. I just figured keeping smbd running up on both servers to reduce failover time. I discovered that I had to share secrets.tdb to ensure that either samba server would remain as a domain member server. Is there another way to do what I am doing? I'd gladly stop sharing this file if I could keep smbd up on both servers. Does smbd need a lock on secrets.tdb? I thought (probably wrong) that only nmbd relied on this file? Further below, you will find some more logs between clients and the server running nmbd and smbd (as the other was sitting idle with smbd running). SJMEMDC05 is a windows domain controller and the other clients are windows explorer clients. When you see these logs, they appear to confirm that secrets.tcb is directly involved, but how would a locking issue with this file cause smbd to go to the D state (and stay)? log.hc-dfinkletest: tdb(/usr/local/samba-3.0.21c/private/secrets.tdb): tdb_lock failed on list 78 ltype=1 (Interrupted system call) log.hc-dfinkletest: tdb_chainlock_with_timeout_internal: alarm (10) timed out for key SJMEMDC05 in tdb /usr/local/samba-3.0.21c/private/secrets .tdb log.hc-dfinkletest: tdb(/usr/local/samba-3.0.21c/private/secrets.tdb): tdb_lock failed on list 78 ltype=1 (Interrupted system call) log.hc-dfinkletest: tdb_chainlock_with_timeout_internal: alarm (10) timed out for key SJMEMDC05 in tdb /usr/local/samba-3.0.21c/private/secrets .tdb log.hc-dfinkletest: tdb(/usr/local/samba-3.0.21c/private/secrets.tdb): tdb_lock failed on list 78 ltype=1 (Interrupted system call) log.hc-dfinkletest: tdb_chainlock_with_timeout_internal: alarm (10) timed out for key SJMEMDC05 in tdb /usr/local/samba-3.0.21c/private/secrets .tdb log.hc-mwang1: tdb(/usr/local/samba-3.0.21c/private/secrets.tdb): tdb_lock failed on list 78 ltype=1 (Interrupted system call) log.hc-mwang1: tdb_chainlock_with_timeout_internal: alarm (10) timed out for key SJMEMDC05 in tdb /usr/local/samba-3.0.21c/private/secrets.tdb log.hc-mwang1: tdb(/usr/local/samba-3.0.21c/private/secrets.tdb): tdb_lock failed on list 78 ltype=1 (Interrupted system call) log.hc-mwang1: tdb_chainlock_with_timeout_internal: alarm (10) timed out for key SJMEMDC05 in tdb /usr/local/samba-3.0.21c/private/secrets.tdb log.hc-mwang1: tdb(/usr/local/samba-3.0.21c/private/secrets.tdb): tdb_lock failed on list 78 ltype=1 (Interrupted system call) log.hc-mwang1: tdb_chainlock_with_timeout_internal: alarm (10) timed out for key SJMEMDC05 in tdb /usr/local/samba-3.0.21c/private/secrets.tdb log.hc-mwang1: tdb(/usr/local/samba-3.0.21c/private/secrets.tdb): tdb_lock failed on list 78 ltype=1 (Interrupted system call) log.hc-mwang1: tdb_chainlock_with_timeout_internal: alarm (10) timed out for key SJMEMDC05 in tdb /usr/local/samba-3.0.21c/private/secrets.tdb log.hc-mwang1: tdb(/usr/local/samba-3.0.21c/private/secrets.tdb): tdb_lock failed on list 78 ltype=1 (Interrupted system call) log.hc-mwang1: tdb_chainlock_with_timeout_internal: alarm (10) timed out for key SJMEMDC05 in tdb /usr/local/samba-3.0.21c/private/secrets.tdb log.hc-mwang1: tdb(/usr/local/samba-3.0.21c/private/secrets.tdb): tdb_lock failed on list 78 ltype=1 (Interrupted system call) log.hc-mwang1: tdb_chainlock_with_timeout_internal: alarm (10) timed out for key SJMEMDC05 in tdb /usr/local/samba-3.0.21c/private/secrets.tdb Thanks, Bill Pappas - System Integration Engineer - SAN St. Jude Children's Research Hospital 332 North Lauderdale Memphis, TN 38105 Danny Thomas Tower - Room D1010 Mail Stop 312 -----Original Message----- From: Jeremy Allison [mailto:[EMAIL PROTECTED] Sent: Saturday, July 22, 2006 10:56 AM To: Pappas, Bill Cc: [EMAIL PROTECTED]; samba@lists.samba.org Subject: Re: [Samba] tdb/tdbutil.c:tdb_chainlock_with_timeout_internal On Fri, Jul 21, 2006 at 06:17:09PM -0500, Pappas, Bill wrote: > I will say this works for weeks on end w/o a problem. When you say this will not work, why? I've had no real problems with the veritas clustered fs. It adheres to file locking and fcntl operations like any normal local filesystem (ext3). Then it might be an intermittent bug in Veritas. What system call is smbd hanging on ? smbd should never hang in the D wait state unless it's a filesystem bug. Jeremy. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
