On Mon, 3 Jul 2006, Francisco Reyes wrote:
Kostik Belousov writes:
I think that then 6.2 and 6.3 is not for you either. Problems
cannot be fixed until enough information is given.
I am trying.. but so far only other users who are having the same problem are
commenting on this and other simmilar threads.
We just need some guidance..
Mark gave me a URL to turn on debugging and volunteered ot give me some
pointers.. I will try, but I will likely try on my own time, on my own
machines.. I can not tell the owner of the company I work for to let me
"try".. or "play around" in production machines.. as we loose customers
because of current problems with the 6.X line.
Since nobody except you experience that problems (at least, only you
notified
about the problem existence)
Did you miss the part of:
User Freebsd writes:
Since there are several of us experiencing what looks to be the same sort
of deadlock issue, I beseech you not to give up
I am not the only one reporting or having the issue.
Careful here, I think this is where things are getting confused ... the
above is related to the deadlock (high vmstat blockd issue), not the NFS
issue ... we're getting two different issues confused :)
improved handling of signals in nfs client. If you could test it, that
would be useful.
Does it matter if the OS is i386 or am64?
Have an amd64 machine I can more easily play with... with no risk to
production.
Does the amd64 machine exhibit the same problem?
----
Marc G. Fournier Hub.Org Networking Services (http://www.hub.org)
Email . [EMAIL PROTECTED] MSN . [EMAIL PROTECTED]
Yahoo . yscrappy Skype: hub.org ICQ . 7615664
_______________________________________________
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
