From: Helge Bahmann <hcb@chaoticmind.net>
Subject: lockd and krb5
Date: Thu, 16 Nov 2006 11:37:27 +0100
Message-ID: <200611161137.28079.hcb@chaoticmind.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
To: nfs@lists.sourceforge.net
Sender: nfs-bounces@lists.sourceforge.net
Errors-To: nfs-bounces@lists.sourceforge.net

Hello,

I am trying to use NFSv3+sec=krb5 for user home directories and I am still 
hitting lockd problems; server is 2.6.18.1 and client is 2.6.17.9

The symptoms are:
- withouth sec=krb5 everything works fine
- with sec=krb5 file locking breaks in strange ways

With sec=krb5:
- processes on the client "hang" waiting for locks
- /proc/locks on the client shows the corresponding files to be not locked
- /proc/locks on the server shows the corresponding files to be locked, by 
processes that do not exist on either the server nor the client (from the pid 
they must be client processes that have exited already)
- sometimes I receive the message "VFS is out of sync with lock manager!"

Unfortunately I have not been able to write a simple testcase, however KDE 
startup triggers the problem very frequently (lots of apps taking a flurry of 
locks and doing funny things with fork)

Can anyone enlighten me what difference sec=krb5 would make with regards to 
locking behaviour so I can narrow down the problem? I am unfortunately 
completely in the dark.

Best regards
-- 
Mathematicians stand on each other's shoulders while computer scientists stand 
on each other's toes.
-- Richard Hamming

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs