tdb locking issue - Solaris 10 and Samba 3.0.33
in [Samba]
|
From: Volker Lendecke on 24 Oct 2009 13:00 On Fri, Oct 23, 2009 at 02:56:48PM -0700, Ray Van Dolson wrote: > On Fri, Oct 23, 2009 at 02:41:46PM -0700, Volker Lendecke wrote: > > On Fri, Oct 23, 2009 at 02:18:19PM -0700, Ray Van Dolson wrote: > > > # pfiles -F 25067 > > > 10: S_IFREG mode:0644 dev:85,60 ino:4630 uid:0 gid:0 size:327680 > > > O_RDWR|O_LARGEFILE > > > advisory read lock set by process 21130 > > > /var/samba/locks/brlock.tdb > > > > Ahhh. What does process 21130 do right now? > > > > That is (was) the PID of the parent smbd process -- the one that spawns > all others. Really? Ok, that might be the CLEAR_IF_FIRST indicator lock. That's probably not the one your problem smbd blocks on. Solaris *must* have a way to figure out who is holding an fcntl lock others want.... Volker
From: Volker Lendecke on 24 Oct 2009 13:00 On Fri, Oct 23, 2009 at 03:09:06PM -0700, Ray Van Dolson wrote: > I'm not sure how to do this either. Guess I could pfiles on every > other PID on the system. See my other mail, this looks like a good hint. > > BTW, you don't happen to run something like samfs? > > > > No SamFS on this environment. Or maybe re-exporting NFS? Volker
From: Volker Lendecke on 24 Oct 2009 13:00 On Fri, Oct 23, 2009 at 02:18:19PM -0700, Ray Van Dolson wrote: > (Yes, I should upgrade Samba to 3.0.35). > > We're running the Sun provided Samba daemon (SUNWsmbau and friends) on > Solaris 10 Generic_138888-08 (sparc). > > Lots of Windows clients (mixed XP, 2003, 2008) hit this server and > periodically we'll start seeing smbd processes begin piling up. These > processes can't be killed with a normal kill -- only kill -9 will do > the trick. Probably someone else is holding the same lock for some reason and is stuck in a file system syscall. Under Linux you would look at /proc/locks to find that info, no idea how to find the current lock holder under Solaris. You need to find that one and see what syscall that guy is stuck in. BTW, you don't happen to run something like samfs? Volker
From: Ray Van Dolson on 24 Oct 2009 13:10 On Fri, Oct 23, 2009 at 02:37:15PM -0700, Volker Lendecke wrote: > On Fri, Oct 23, 2009 at 02:18:19PM -0700, Ray Van Dolson wrote: > > (Yes, I should upgrade Samba to 3.0.35). > > > > We're running the Sun provided Samba daemon (SUNWsmbau and friends) on > > Solaris 10 Generic_138888-08 (sparc). > > > > Lots of Windows clients (mixed XP, 2003, 2008) hit this server and > > periodically we'll start seeing smbd processes begin piling up. These > > processes can't be killed with a normal kill -- only kill -9 will do > > the trick. > > Probably someone else is holding the same lock for some > reason and is stuck in a file system syscall. > > Under Linux you would look at /proc/locks to find that info, > no idea how to find the current lock holder under Solaris. > You need to find that one and see what syscall that guy is > stuck in. I'm not sure how to do this either. Guess I could pfiles on every other PID on the system. I know there are other PID's also in the same state, trying to get what appears to be the same lock... > > BTW, you don't happen to run something like samfs? > No SamFS on this environment. > Volker Thanks! Ray -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
From: Volker Lendecke on 24 Oct 2009 13:10
On Fri, Oct 23, 2009 at 02:18:19PM -0700, Ray Van Dolson wrote: > # pfiles -F 25067 > 10: S_IFREG mode:0644 dev:85,60 ino:4630 uid:0 gid:0 size:327680 > O_RDWR|O_LARGEFILE > advisory read lock set by process 21130 > /var/samba/locks/brlock.tdb Ahhh. What does process 21130 do right now? Volker |