Thanks for all the info, 'hard' did the job well.
Best regards, Rafal Radecki.
2013/7/12 Jeremy Webber jeremy.webber@al.com.au
On 11/07/2013, at 7:14 PM, Rafał Radecki wrote:
I think that if I use nfs version 3 and hard mount option on clients they will not see any problems during takeover/giveback. What do you think about using 'hard' on clients when they connect to netapp shares and takeover/giveback is performed?
'*hard*' is appropriate when you are using applications which can't fail gracefully if their data goes away. In practise that is almost all of them so we always use 'hard'. You probably want to use '*intr*' as well, this permits you to interrupt (kill) processes which have hung because their NFS server went away.
'*soft*' would be useful if you have an application which could fail gracefully in the event that its data went away. A case I can think of is where you have a web server providing a UI for an application, where the UI could revert to a sensible error message in the event that the NFS server (holding the application data) went offline.
To be honest, I have never seen the latter case in practise, but maybe there are some out there.
Another possible use case is if you have a very unreliable NFS server, but that wouldn't be a production environment would it?
To enable takeover/giveback to be transparent to clients (apart from the brief hang) you definitely would want to use 'hard', though 'soft' may work if the timeout is greater than 180 seconds.
HTH, Jeremy
-- Jeremy Webber Senior Systems Engineer Animal Logic Pty Ltd T: +61 2 9383 4837 F: +61 2 9383 4801
Toasters mailing list Toasters@teaparty.net http://www.teaparty.net/mailman/listinfo/toasters