Question on IPv6 failover.
Subsystems (2)
One of our users is reporting that the CIFS failover case is not working properly. They have a cluster of CIFS servers that migrate an IPv6 addr to the active system.
Evidently, our client-side CIFS connection follows the first migration, but fails to go back to the original on a second failover.
It could be any number of things, but I wanted first to see if anyone knows how long client-side CIFS will keep attempting to regain contact with it's server? Forever?
Thanks,
Ben
Signature · 2 lines
Ben Greear <greearb-my8/[email protected]> Candela Technologies Inc http://www.candelatech.com
Quoted 7 lines · Ben Greear
One of our users is reporting that the CIFS failover case is not working properly. They have a cluster of CIFS servers that migrate an IPv6 addr to the active system.
Evidently, our client-side CIFS connection follows the first migration, but fails to go back to the original on a second failover.
Quoted 7 lines
It could be any number of things, but I wanted first to see if anyone knows how long client-side CIFS will keep attempting to regain contact with it's
server? Forever?Thanks,
Ben
Depends on kernel version and also hard vs. soft (default) mount options.
The "smb echo" approach that cifs moved to a few years ago allows the cifs kernel client to notice more quickly that the server is down, and significantly improved failover.
Which kernel version?
Signature · 3 lines
Thanks, Steve
Quoted 16 lines · Steve French
Quoted 7 lines · Ben Greear
One of our users is reporting that the CIFS failover case is not working properly. They have a cluster of CIFS servers that migrate an IPv6 addr to the active system.
Evidently, our client-side CIFS connection follows the first migration, but fails to go back to the original on a second failover.
Quoted 7 lines
It could be any number of things, but I wanted first to see if anyone knows how long client-side CIFS will keep attempting to regain contact with it's
server? Forever?Thanks,
Ben
Quoted 7 lines
Depends on kernel version and also hard vs. soft (default) mount options.
The "smb echo" approach that cifs moved to a few years ago allows the cifs kernel client to notice more quickly that the server is down, and significantly improved failover.
Which kernel version?
3.7.10
The hard v/s soft is not being specified when mounting unless the customer did something interesting, so I guess it is soft.
I'm still waiting on a network dump, so at this time I have no reason to believe that Linux CIFS is actually to blame...just trying to understand the possibilities better.
Thanks,
Ben
Signature · 2 lines
Ben Greear <greearb-my8/[email protected]> Candela Technologies Inc http://www.candelatech.com
Quoted 11 lines · On Thu, 03 Oct 2013 14:04:55 -0700 Ben Greear…
One of our users is reporting that the CIFS failover case is not working properly. They have a cluster of CIFS servers that migrate an IPv6 addr to the active system.
Evidently, our client-side CIFS connection follows the first migration, but fails to go back to the original on a second failover.
It could be any number of things, but I wanted first to see if anyone knows how long client-side CIFS will keep attempting to regain contact with it's server? Forever?
Yep, forever. The address to connect to is determined by the mount helper and passed down to the kernel at mount time. This is the same for IPv4 and IPv6. If the address is floating between servers then it'll just look like the server rebooted when you fail over, and the client should just keep trying to reconnect indefinitely.
Signature · 1 line
Jeff Layton <[email protected]>