Bernd Schubert wrote:
Hello,
on servers with heartbeat managed resources one rather often has the situation
one exports different directories from different resources.
It now may happen all resources are running on one host, but they can also run
from different hosts. The situation gets even more complicated if the server
is also a nfs client.
In principle having different nfs resources works fine, only the statd state
directory is a problem. Or in principle the statd concept at all. Actually we
would need to have several instances of statd running using different
directories. These then would have to be migrated from one server to the
other on resource movement.
However, as far I understand it, there does not even exist the basic concept
for this, doesn't it?
The efforts have been attempted (to remedy this issue) and a complete
set of patches have been (kept) submitting for the past two years. The
patch acceptance progress is very slow (I guess people just don't want
to get bothered with cluster issues ?).
Anyway, the kernel side has the basic infrastructure to handle the
problem (it stores the incoming clients IP address as part of its
book-keeping record) - just a little bit tweak will do the job. However,
the user side statd directory needs to get re-structured. I didn't
publish the user side directory structure script during my last round of
submission. Forking statd into multiple threads do not solve all the
issues. Check out:
https://www.redhat.com/archives/cluster-devel/2007-April/msg00028.html
-- Wendy
--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
