With clustered NFS the writes should be synchronous so they get committed to stable storage before the client gets confirmation the write completed. As a result the write is on disk so there is no corruption after a reboot or failover. On Wednesday 26 August 2009 01:55:24 am Mike Cardwell wrote: > On 25/08/2009 20:40, Mike Cardwell wrote: > > I figured that failover would happen more smoothly if the client was > > aware of and in control of what was going on. If the IP suddenly moves > > to another NFS server I don't know how the NFS client will cope with > > that. > > Well, it seems to cope quite well. The nfs mount "hangs" for a few > seconds whilst the IP moves from one server to another (unavoidable > obviously), but it then picks up from where it was. I suspect there will > be file corruption issues with files that are partially written when the > failover happens, but I guess that can't be avoided without a client > side solution. -- Dwight Hubbard Owner Effective Automation Solutions Website: http://effectiveautomationsolutions.com Email: dwight@xxxxxxxxxxxxxxxxx Phone: (503) 941-0327 Redhat Certified Engineer - RHCE #804007137224095 VMware Certified Professional - VCP #18529 -- Linux-cluster mailing list Linux-cluster@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/linux-cluster
