mattlach
Patron
- Joined
- Oct 14, 2012
- Messages
- 280
Hey all,
Does it?
Otherwise I have a weird problem I can't wrap my head around.
My FreeNAS server has two NFS shares set up. One shares server storage traffic over a 10gig interface. This interface is dedicated to storage traffic, and is on a different subnet from the main interface which is used for connecting clients, web interface configuration and ssh.
The problem is with my main client share. My clients are a mix of linux, mac and windows machines. My Main desktop is on linux, and has for the longest time been set up to have two NFS shares over this client interface.
Yesterday, I added a second Linux client IP using the space delimited format called for on the share screen. I didn't change anything else, just added an IP to the "allowed IP addresses" section. The new linux client mounted the NFS share just fine.
Everything was hunky dory, until I noticed that my main Linux desktop all of a sudden no longer mounts its two NFS shares.
Odd, I thought, maybe I accidentally deleted a digit of the IP address in the "allowed IP addresses section". Nope, that checked out. Then I raised the NFS servers maximum allowed connections, just in case that was the problem. Hit save. Desktop still times out when trying to mount shares, without me ever changing anything on the client side...
The kicker is, the new client for which I added the IP address still connects just fine, as do both the servers on the internal storage traffic 10gig network...
The only thing I can think of that might be causing the problem is if the NFS daemon needs to be restarted after changing the number of allowed servers for it to take effect, but I can't test that theory right now, as I have some critical traffic from one of the servers to FreeNAS right now, and don't want to reset the link.
What do you guys think. Does changing the number of servers require a NFS daemon restart, or FreeNAS system reboot, or am I up against something else weird going on here?
Much obliged,
Matt
Does it?
Otherwise I have a weird problem I can't wrap my head around.
My FreeNAS server has two NFS shares set up. One shares server storage traffic over a 10gig interface. This interface is dedicated to storage traffic, and is on a different subnet from the main interface which is used for connecting clients, web interface configuration and ssh.
The problem is with my main client share. My clients are a mix of linux, mac and windows machines. My Main desktop is on linux, and has for the longest time been set up to have two NFS shares over this client interface.
Yesterday, I added a second Linux client IP using the space delimited format called for on the share screen. I didn't change anything else, just added an IP to the "allowed IP addresses" section. The new linux client mounted the NFS share just fine.
Everything was hunky dory, until I noticed that my main Linux desktop all of a sudden no longer mounts its two NFS shares.
Odd, I thought, maybe I accidentally deleted a digit of the IP address in the "allowed IP addresses section". Nope, that checked out. Then I raised the NFS servers maximum allowed connections, just in case that was the problem. Hit save. Desktop still times out when trying to mount shares, without me ever changing anything on the client side...
The kicker is, the new client for which I added the IP address still connects just fine, as do both the servers on the internal storage traffic 10gig network...
The only thing I can think of that might be causing the problem is if the NFS daemon needs to be restarted after changing the number of allowed servers for it to take effect, but I can't test that theory right now, as I have some critical traffic from one of the servers to FreeNAS right now, and don't want to reset the link.
What do you guys think. Does changing the number of servers require a NFS daemon restart, or FreeNAS system reboot, or am I up against something else weird going on here?
Much obliged,
Matt