[[ Reply by email or post, don't do both ]]
>I think what you nead is to mount "soft" instead of the default "hard."
No, don't use soft.
(If you use soft mounts on r/w filesystem, you needn't bother with backups)
Quote:>Soft mounts are in general not recommended in the NFS manual, but we plan to use
>it here in a case where if we can't write to a file mounted from a primary server,
>we
>have the app attempt to write to a secondary server. With a hard mount, the app
>would hang waiting until the link with the primary server came back. In a
>production
>environment, this would be most undesireable.
Yes, but you should remember that whatever timeout you chose for softmounts,
it will always be shorter than short temporary outage (of network/whatever).
My experience is that you get NFS timeout occasionally, even in a fully
functional net (traffic peaks, etc).
Any NFS server not responding emssaeg you see now, will translate to
(possibly unnoticed) application data loss.
You can interrupts writes to hard mounted filesystems, look into
that instead.
Casper
--
Expressed in this posting are my opinions. They are in no way related
to opinions held by my employer, Sun Microsystems.
Statements on Sun products included here are not gospel and may
be fiction rather than truth.
by