Jorgen Lundman wrote: > > > Which works without issue. So it is not an NFS problem, it seems to be > related to alias IPs. > > Do you know a way around this? Or perhaps you can suggest a place > where I can go to ask. As a quick solution we will just forgo the > Alias IP and mount directly on the "real" IP. Why can I change > protocol (TCP->UDP and vv) to get around it, why can I reboot the NFS > client as well. Did we create the aliases wrong? > > I apologise for the noise in NFS discussion list. > > Lund
Jorgen, Noise, no, this is not noise. I just think most people are overloaded right now with getting ready for Connectathon 2009. (www.connectathon.org) You have an interesting problem, please follow-up to the list with a summary of what you find. That will eventually help the next person who hits this issue and understands how to use google as well. Thanks, Tom PS: One of the things I used to get struck by as a developer who got customer escalations was their definition of what was NFS and my colleagues definition of NFS. After all, we worked deep in the protocol, the system, etc. Our definition is very narrow, very focused. And a customer tends to think in broader systems - NFS is an application to them. What a developer has to realize is that their subsystem can not exist in a vacuum - nfs means nothing if the DNS server does not do reverse name mapping in a timely fashion. And what the customer has to realize is that the developer may be an expert in the subsystem, but clueless as to how it is used in real world systems. I remember once releasing a new feature that we planned on deprecating (at a previous company). In 6 months, when we went to deprecate it, we found we couldn't as customers were using it to solve problems other than the ones I envisioned. Going to the problem at hand, I wonder how many developers commonly use an IP alias in their day to day testing? Within the NFS group, I'm confident in saying none. But someone in say a clustering group may do so daily. (No clue if they are the ones who can solve your problem.)