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 will try to setup the environment, but to be honest no more 6.X for us
until 6.2 or 6.3.. We have lost clients already.
Is this a problem that you can easily recreate
There is one thing I can easily recreate that would very helpfull to solve.
The 6.X NFS clients freeze if the NFS server goes away.
I have been able to reproduce that every single time.. both in test and
production.
machine? In my case, I have one machine fully configured for debugging,
Although solving both, server and client, would be great for us if we could
at least solve the client.. it would be very helpfull.. until our next
server comes.. in which we are going to install 5.5
information to the developers to debug this, the faster it will get fixed
Agree.. but with 4+ crashes in less than a week it has reached the point
where we have moved workload away from the most problematic machine.. to try
to aliviate the problem.. but still was not enough.. to prevent at least one
big customer of ours to go.. We don't keep tight track of the smaller ones.
:-)
different then your auto-mechanic ... try telling him there is a 'knocking
under the hood, please tell me how to fix it, but you can't have my car',
and he'll brush you off ... give him 30 minutes under the hood, and not
only will he have identified it, but he'll probably fix it too ...
The problem is when you are a taxi driver... and it cost you money to have
the car off the streets.. and you don't know when the 'knocking' will
occur... :-)
Will setup my laptop with the debug settings and will then work on trying to
debug the client problem... depending on how that goes will then possibly
try the server that is giving us problems.
_______________________________________________
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
