[opensuse-factory] Re: [opensuse-edu] Re: NFS
hey guys.. i have the exact same issue. i do not have any "mac" clients... my server is SLES x86_64 and all my clients are openSUSE11.1 i586 i have those freeze several times, but i wasnt able yet to understand why. any help is really appreciate Andrea Il 13/11/2009 16:47, James Tremblay aka SLEducator ha scritto:
Phil, I would imagine that the rpclock provided by Apple is tuned for Apple clients. Then add the 32-64 mystery and well , I don't know. The first thing I would try is a 64 bit openSUSE client. I am forwarding this to the team to see if someone else can help. My Brother a "Mac Fan" is not sure either. Keep in touch JT
Phil Grace wrote:
James, how are you doing? I just have a quick opensuse edu question that I thought if anyone knew the answer to, you would. We've been using Opensuse 11.1 in our Highschool library for a while now very successfully with an OS X server setup. The linux clients authenticate via ldap and access their homefolders via NFS. Everything has worked smoothly until I upgraded the home folder server to snow leopard which has NFS running at 64bit.
Now the opensuse clients are freezing. I was figuring that the issue is because the clients are 32 bit and when the linux apps are locking files in use they are doing so as 32 bit, but the files actually reside on the 64 bit server. When the linux clients freeze I notice that rpclock.d on the server is hogging resources, when I stop it and restart NFS it starts working again.
Is there anything you can recommend I change on the client side maybe NFS locking settings or something that will prevent me from needing to go back to 32 bit on the server or going up to 64 bit on the clients?
Thanks for any direction you can provide
Phil Grace Technology Director Heber Springs School District pgrace@hssd.k12.ar.us
-- ------------------------------------------ Andrea Florio QSI International School of Brindisi Sys Admin openSUSE-Education Administrator openSUSE Official Member (anubisg1) Email: andrea@opensuse.org Packman Packaging Team Email: andrea@links2linux.de Web: http://packman.links2linux.org/ Cell: +39-328-7365667 ------------------------------------------ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Fri, 2009-11-13 at 18:49 +0100, Andrea Florio wrote:
hey guys.. i have the exact same issue. i do not have any "mac" clients... my server is SLES x86_64 and all my clients are openSUSE11.1 i586
i have those freeze several times, but i wasnt able yet to understand why. any help is really appreciate
Any chance of running xen on the same machine? (That is apperently a forbidden combination..) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Fri, 2009-11-13 at 18:49 +0100, Andrea Florio wrote:
hey guys.. i have the exact same issue. i do not have any "mac" clients... my server is SLES x86_64 and all my clients are openSUSE11.1 i586
i have those freeze several times, but i wasnt able yet to understand why. any help is really appreciate
Andrea
Perhaps worthwhile trying... I had identical lockups This evening i noticed (while doing an iostat in another screen) that a regular "sync" caused a large buffer to flush, and files (on a nfs-client) to be updated. Now i do on the nfs-server (in the background) this: #!/bin/bash for ((;;)) do sync; sleep 10; done And my problems did not show up for several hours. i know, it's NOT a solution, but it keeps my nfs-server from locking up. hw -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
2009/11/13 Andrea Florio <andrea@opensuse.org>:
Now the opensuse clients are freezing. I was figuring that the issue is because the clients are 32 bit and when the linux apps are locking files in use they are doing so as 32 bit, but the files actually reside on the 64 bit server. When the linux clients freeze I notice that rpclock.d on the server is hogging resources, when I stop it and restart NFS it starts working again.
Just on Friday I read on Novell website the "Golden Rule", if things are working well don't change them! :) This looks Apple Snow Leopard has an NFS issue, for some reason the NFS locking daemon has always been requiring regular patching. Some things don't seem to change much, Sun could never get NFS locking daemon right, even in the old SunOS days with a simpler protocol.
Is there anything you can recommend I change on the client side maybe NFS locking settings or something that will prevent me from needing to go back to 32 bit on the server or going up to 64 bit on the clients?
It shouldn't be 32 bit v 64 bit, what goes over the wire is defined by the RPC layer, and has to use defined byte order and size of fieldd, it is independant of CPU or NFS would never have worked as well as it did. A quick Google shows Apple have 'enhanced' NFSv3 server claiming 2x performance, most likely they need to patch it. http://www.apple.com/server/macosx/performance.html One could experiment to confirm the clients file locking is torturing the server, by using the 'nolock' mount option on the client. If each client has a different login in use rather than sharing directories, then most likely locks in /home/$USER are not really uncessary. It was most often directories like /var/spool/mail that would require locking, to avoid incoming Email corrupting mail boxes that were being processed by clients. Rob Disclaimer : I do not run Apple OSX, and base my answer on past experience of running NFS servers commercially. Treat it as informed speculation only. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
participants (3)
-
Andrea Florio -
Hans Witvliet -
Rob OpenSuSE